Fix for latency warnings
For those seeing the recent event latency warnings, I've just put in a fix
** (inkscape:27965): WARNING **: Event latency reached 3.290566 sec
The main cause of extraneous warnings is a slight difference between the clock used for the GDK event marking and the real time. On my Mac, I observed that the skew was of a constant factor, so I added in an option to compensate for that. On my system the value was 0.9766 (and thus on my system after running for 85 seconds Inkscape would believe a latency of over 2 seconds had crept in).
We'll probably need to investigate this a bit more, but getting that factor in should let people with false warnings get things calibrated and see only good ones.
If you need it, look for the new setting under the misc pane.
On Sat, Jul 26, 2008 at 5:17 AM, Jon A. Cruz <jon@...18...> wrote:
The main cause of extraneous warnings is a slight difference between the clock used for the GDK event marking and the real time. On my Mac, I observed that the skew was of a constant factor, so I added in an option to compensate for that. On my system the value was 0.9766 (and thus on my system after running for 85 seconds Inkscape would believe a latency of over 2 seconds had crept in).
Wow, are you saying I have to calculate this coefficient to 1e-4 precision and type it into prefs, just in order to suppress a warning?
I may have missed the explanation (sorry), but I still don't understand what the specific benefit of these warnings is. If they just tell me that Inkscape is running slow, then thank you very much but I can feel that very well without any warnings. Can they be used to pinpoint where exactly the slowness happens in the code? If so how, and how is it better than profiling?
On Jul 26, 2008, at 8:19 AM, bulia byak wrote:
Wow, are you saying I have to calculate this coefficient to 1e-4 precision and type it into prefs, just in order to suppress a warning?
No. I'm adding that calculation to be included in the warning itself.
I may have missed the explanation (sorry), but I still don't understand what the specific benefit of these warnings is. If they just tell me that Inkscape is running slow, then thank you very much but I can feel that very well without any warnings. Can they be used to pinpoint where exactly the slowness happens in the code? If so how, and how is it better than profiling?
What it will do is flag things when events start to pile up, and list to what degree they are getting delayed. It can be *very* useful for things such as checking how different display options, filter settings, etc. affect things.
Mental can list more details of the usefulness, since he's the one who added it to begin with.
participants (2)
-
bulia byak -
Jon A. Cruz