Starting with temBoard version 7.10, Dalibo implemented a quite interesting feature in regards to tracing performance related issues.
Whenever performance related issues pops up, it was not so easy to identify what component of the temBoard UI was causing it. It could have temboardui: [monitoring], temboardui: [tools], temboardui: [statements], SQL’s running against the repository DB, scheduled jobs, or many other.
In case you are running temBoard version 7.10 or higher, you can now enable performance tracing. To do so, you need to adjust two files. The temBoard systemd service file and the temboard.conf file.
Add Environment=PERF=y to the systemd drop-in file:
$ cat /etc/systemd/system/temboard.service.d/override.conf [Service] Nice=-19 Environment=PERF=y
Add the DEBUG logging level:
$ cat /etc/temboard/temboard.conf ... ... [logging] level = DEBUG ...
Afterwards reload the systemd daemon, and restart temBoard service.
$ sudo systemctl daemon-reload $ sudo systemctl stop temboard.service $ sudo systemctl start temboard.service
That’s it. Now you should see performance related messages in the temboard.log file.
...
2022-01-27 12:35:36,257 [2673406] [taskmanager ] DEBUG: Activate worker purge_data_worker
2022-01-27 12:35:36,260 [2673427] [services ] INFO: Starting worker pool.
2022-01-27 12:35:36,261 [2673406] [services ] INFO: Starting web.
2022-01-27 12:35:36,262 [2673427] [perf ] DEBUG: Scheduling perf counters each 15 seconds.
2022-01-27 12:35:36,262 [2673428] [services ] INFO: Starting scheduler.
2022-01-27 12:35:36,262 [2673406] [perf ] DEBUG: Scheduling perf counters each 15 seconds.
2022-01-27 12:35:36,263 [2673427] [perf ] DEBUG: io_rchar=0 io_wchar=184 pid=2673427 service=worker-pool stime=0.0 utime=0.0 vsize=116420608
2022-01-27 12:35:36,263 [2673406] [perf ] DEBUG: io_rchar=9610041 io_wchar=108165 pid=2673406 service=web stime=0.05 utime=0.66 vsize=116420608
2022-01-27 12:35:36,263 [2673427] [services ] DEBUG: Entering worker pool loop.
2022-01-27 12:35:36,263 [2673428] [perf ] DEBUG: Scheduling perf counters each 15 seconds.
2022-01-27 12:35:36,263 [2673428] [perf ] DEBUG: io_rchar=0 io_wchar=182 pid=2673428 service=scheduler stime=0.0 utime=0.0 vsize=116420608
2022-01-27 12:35:36,264 [2673428] [taskmanager ] DEBUG: Update Task aggregate_data with options={}
...
In case you want to learn more about this new feature, check out the following links:
https://temboard.readthedocs.io/en/v7/howto-temboard-performances/#enabling-performance-tracing
Conclusion
A great feature in regards of performance tuning. It gives you so much more insites of what is happening behind the scenes. And don’t forget to disable the DEBUG mode, after you have gathered enough information.