softsyst
commented
2 months ago Heiko,
many thanks for this observation. Although there is nothing wrong with it, the many accesses to the config file seem to put some - perhaps avoidable - load on the system. I missed that.
A quick inspection showed that the thread id is the one of the main GUI, as I expected. The file accesses are probably the reading of some directories from the config file, for instance to continuously get the icon files of the DAB services. This should all be triggered by timer functions which run about every 100ms or so. Thus, I'll inspect this further to find out where that high frequency comes from. The GUI in its complexity runs many timers, but not all should access the config file so regularly. According to your measurements, it happens about every 6.5ms, which is an average though.
I certainly agree that it should be investigated, and I'll do as soon as I find the time.
Clem
Hi Clem!
Procmon says that the QIRX-thread which processes "qirx4.config" is running wild most of time. It opens/reads/closes this file more than 10800 times in 70 seconds. There are some longer "breaks" (500ms; see the times at the marked line in the pic below) in between, but most of time it only takes a break when the system stops the thread for some milliseconds. Well, the file is memory-mapped, shared and unaltered (most of times), so the question is: What's up with this thread?
BFN Heiko