Support #8718
openAbout Wt.WT.updateDelay
0%
Description
I found that changing Wt.WT.updateDelay = 0; speed up the localhost app a lot.
It also have effect with online app https://webtoolkit.eu/widgets/graphics-charts/paintbrush
Try execute console Wt.WT.updateDelay = 0; The paint widget is much better.
I try it with our large application and your website, it work fine.
I'd like to know what is the reason of Wt.WT.updateDelay?
Should I adjust this? What is the potential problem if I change it?
Updated by Korneel Dumon over 3 years ago
I think the idea is to batch these fast paced events like mouseOver, so that you don't get a massive amount of separate requests to the server. I never really noticed that the paintbrush was particularly slow.
We have a few components (eg. 3d charts) in Wt that require low latency and in that case, we implement the functionality in javascript.
Updated by Apivan Tuntakurn over 1 year ago
Thank you for your response! While I don't think that Wt is slow in general, I have noticed that when deployed on a local network or through WebView, setting Wt.WT.updateDelay to 51 results in a maximum of 20fps. However, by lowering this value, I was able to achieve higher fps rates than my monitor can display. I suggest that this feature be documented or made configurable, so that users are aware of its impact. When benchmarking Wt against other frameworks, it's important to take this into consideration.