Re: [Tigervnc-devel] The deferred update timer

2011-12-09 Thread DRC
All of these arguments are red herrings. As I indicated in my previous post, the current deferred update timer setting reduces performance both in a low-latency and a high-latency environment. The drop in performance from using a 10 ms DUT was much the same whenever I artificially simulated 200 m

Re: [Tigervnc-devel] The deferred update timer

2011-12-09 Thread Pierre Ossman
On Wed, 07 Dec 2011 04:39:40 -0600 DRC wrote: > > This is an Amdahl's Law thing. The frame rate is capped to 1 / > ({deferred update time} + {FBU processing time}). Whether or not the > FBU processing time is all CPU or some CPU and some I/O is irrelevant. > As long as the server can't receive

Re: [Tigervnc-devel] The deferred update timer

2011-12-07 Thread DRC
On 12/7/11 2:44 AM, Pierre Ossman wrote: >>> Annoying. I did some work at making the thing more asynchronous, but >>> more might be needed. If the problem is getting the data on the wire >>> rather than the actual encoding, then a quick fix is increasing the >>> outgoing buffer size. As long as you

Re: [Tigervnc-devel] The deferred update timer

2011-12-07 Thread Pierre Ossman
On Fri, 02 Dec 2011 04:14:14 -0600 DRC wrote: > On 12/2/11 3:19 AM, Pierre Ossman wrote: > > Annoying. I did some work at making the thing more asynchronous, but > > more might be needed. If the problem is getting the data on the wire > > rather than the actual encoding, then a quick fix is incre

Re: [Tigervnc-devel] The deferred update timer

2011-12-02 Thread DRC
On 12/2/11 3:19 AM, Pierre Ossman wrote: > Annoying. I did some work at making the thing more asynchronous, but > more might be needed. If the problem is getting the data on the wire > rather than the actual encoding, then a quick fix is increasing the > outgoing buffer size. As long as your entire

Re: [Tigervnc-devel] The deferred update timer

2011-12-02 Thread Pierre Ossman
On Thu, 01 Dec 2011 18:01:32 -0600 DRC wrote: > When the deferred update timer behavior was recently overhauled such > that it pushes out updates whenever the timer is triggered rather than > waiting for an update request from the client, the default DUT value was > also changed to 10 ms (from 1

[Tigervnc-devel] The deferred update timer

2011-12-01 Thread DRC
When the deferred update timer behavior was recently overhauled such that it pushes out updates whenever the timer is triggered rather than waiting for an update request from the client, the default DUT value was also changed to 10 ms (from 1 ms.) Unfortunately, setting the DUT to 10 ms results in