Test KDevelop4 with --graphicssystem native
Aleix Pol
aleixpol at kde.org
Sat Nov 21 21:30:25 UTC 2009
On Sat, Nov 21, 2009 at 10:25 PM, David Nolden <zwabel at googlemail.com>wrote:
> Am Samstag 21 November 2009 22:14:10 schrieb Aleix Pol:
> >
> > Works fine here with both raster and native, but I guess using native
> will
> > be better.
> >
> > Why don't we stop forcing raster for now? If it's outperforming we can go
> > back to force raster in january. It's something hard to measure, it's
> more
> > like a feeling I guess.
> >
> > Aleix
>
> The problem is that you might not feel the difference during a fast shallow
> test, but only during 'real' usage. From what I remember, native vs. raster
> was a giganting performance difference in the completion-list in the past:
> Start code-completion at some place where there is really many completion
> items visible, and then scroll through the list by keeping "PGDOWN"
> pressed.
>
> Another important test: In a large file with a lot of semantic
> highlighting,
> use the scrollbar to scroll up and down the document really fast, and
> measure
> the _felt_ lag between scrolling and painting.
>
That was what I was trying (and what annoyed me when we moved to raster).
I'm using 4.6 so maybe this has improved a bit, i'm not sure.
>
> Greetings, David
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20091121/1ffedc7d/attachment.html>
More information about the KDevelop-devel
mailing list