Community
Participate
Working Groups
The performance tests in SWT show a slowdown of 66% on Windows and 100% on GTK. Billy said that this was because the test was not reasonable for comparing against 3.0 and needs updating.
Grant and Silenio, Can you look at these tests and decide what is reasonable? Thank you, Veronika
Tod, which build showed these and which tests in particular? Going from N20050307-0010 I see the following GC tests stand out: Windows - GC.setLineWidth() -70% GTK+ - new GC(Drawable) -70%,-100% - GC.getClipping -195% - GC.copyArea -100% - GC.drawImage -100% GC.drawImage() and GC.copyArea() on Linux are completing in less than 200 milliseconds each, and the times are highly variable. These results are noise and maybe the tests should be removed or fixed.
This is the build I saw the issues in too.
Created attachment 18889 [details] Patch GC.getClipping() became slower in revision 1.67 which added the damage region. The extra cost is from creating a new region which we just use to get the bounding box. This patch optimizes this case.
I am finding it difficult to explain the change for the new GC(Drawable) benchmark. Besides the locking changes, the only addition of code is that we now set data.background and data.foreground in Image.internal_new_GC() and that we call pango_context_set_base_dir() in GC.init(). Neither of these changes seem to make much difference in performance here though.
Reassigning to me and changing the subject to reflect what came out of this.
Note that this may be fixed already.
Closing the bug as this is against very old swt release and too many underlying things changed since then. Please open a separate bug report if you have measurable slow down with 4.3.
