On Sunday 07 May 2006 21:47, Jure Varlec wrote: > So now I mostly understand what this does. But the way the clock acts still > seems funny. Where could that "jump" come from? 100Hz seems too high for > that, unless I'm missing something.
I played with it some more. Only with superkaramba for now, as this is where it's most apparent (haven't noticed this "jump/skip" anywhere else for now). This "jump" seems to happen when I have multiple themes and/or sensors set to the same update interval of 1 sec, i.e. when there are many processes starting up at the same moment. As the timer frequency relates to the process scheduler, I now believe that with such a low frequency not all processes manage to complete their tasks within the update interval. Therefore some of them update too late. But why another update so soon after the last one? It makes me think two updates get stacked and then both processed at the same time. Pha. It's bloody obvious I haven't a clue about how this is all implemented. While it's not an issue to be solved, it's interesting and I'd appreciate if someone can explain this to me.
pgp8hHpLRuSgN.pgp
Description: PGP signature
