🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

5 minute vmr-solaudit cpu spikes

RobertHau
RobertHau Member Posts: 4
edited December 2021 in PubSub+ Event Broker #1

python3 /usr/sw/loads/soltr_9.9.0.34/scripts/vmr-solaudit -d --daemonize

does anyone else see a curious 5 minute cpu spike on the PubSub+

02:40:46 PM 1000001 18428 16.00 6.00 0.00 22.00 2 python3
02:40:47 PM 1000001 18428 76.00 24.00 0.00 100.00 2 python3
02:40:48 PM 1000001 18428 55.00 21.00 0.00 76.00 3 python3

02:45:49 PM 1000001 18428 19.00 6.00 0.00 25.00 0 python3
02:45:50 PM 1000001 18428 75.00 25.00 0.00 100.00 0 python3
02:45:51 PM 1000001 18428 76.00 23.00 0.00 99.00 0 python3
02:45:52 PM 1000001 18428 7.00 3.00 0.00 10.00 0 python3

Strace shows this at the time for the pid.

Answers

  • RobertHau
    RobertHau Member Posts: 4
    edited December 2021 #2

    Any Answer is helpful.

  • Tamimi
    Tamimi Member, Administrator, Employee Posts: 541 admin

    Interesting, I'm kind of curious about your setup - can you pleases have more details?

    • Is this happening when you are running a client using the Python API?
    • Does this happen only when you have a local docker broker running?
    • What activity are you doing when this happens/
  • RobertHau
    RobertHau Member Posts: 4
    edited December 2021 #4

    @Tamimi said:
    Interesting, I'm kind of curious about your setup - can you pleases have more details?

    • Is this happening when you are running a client using the Python API?
    • Does this happen only when you have a local docker broker running?
    • What activity are you doing when this happens/

    This is happening when just the broker is running.

    There is next to nothing being written to the log short of semp commands.

    0 drwxrwxrwx 1 root    root      105 Nov 29 21:02 ..
    4 -rw------- 1 appuser root     2022 Nov 29 21:02 kernel.log
    

    16 -rw------- 1 appuser root 13168 Nov 29 21:02 system.log
    236 -rw------- 1 appuser root 240340 Dec 1 13:05 debug.log
    0 drwx------ 2 appuser root 160 Dec 1 14:06 .
    31148 -rw-rw-rw- 1 appuser root 31894782 Dec 1 14:07 gather-diagnostics_2d_solaceVMRap_2021-12-01T14.06.58.tgz
    712 -rw------- 1 appuser root 728315 Dec 1 19:27 event.log
    4800 -rw------- 1 appuser root 4430141 Dec 1 19:27 command.log

  • RobertHau
    RobertHau Member Posts: 4

    It appears to be caused by "Garbage Collection" on the PubSub+

    When looking at this it doesn't to be the most optimal or efficient process.