Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
scintilla-interest
Home
About this group
Apply for group membership
Message from discussion Where to look for performance issues
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Lex Trotman  
View profile  
 More options Jul 30 2012, 10:34 pm
From: Lex Trotman <ele...@gmail.com>
Date: Tue, 31 Jul 2012 12:34:53 +1000
Local: Mon, Jul 30 2012 10:34 pm
Subject: Re: [scintilla] Where to look for performance issues
Print | View thread | Show original | Report this message | Find messages by this author
On 2 July 2012 11:31, Neil Hodgson <nyamaton...@me.com> wrote:

> Lex Trotman:

>> In Geany we are experiencing slowing of performance after a file has
>> been open and edited all day.  The effect is that some screen paints
>> can be visibly slow.

>> So far we have measured ScintillaGTK::ExposeTextThis as normally
>> taking less than 10ms, but when the slowdown is visible sometimes it
>> can take more than 150ms, and sometimes the normal <10ms.  The same
>> file just open all day but not edited shows about 50ms sometimes.

>    Over that period, I'd suspect memory or resource issues. Check whether there is more memory being used than at the start.

>    Breaking the 150ms down further into individual methods or lines would help discover the underlying issue. Just breaking the ExposeTextThis time into PaintSelMargin, Paint before painting lines, painting each line, and painting after lines would be useful. Measure time spent in each notification to the host app. Check whether wrap is on - mode wrap can be much slower and memory intensive than normal painting.

>    Neil

Hi Neil,

Quick follow up, the problem appears to be due to the use of
INDIC_SQUIGGLE for compile errors and spelling errors, when there is a
significant amount of indicator the performance slows way down.
Switching to INDIC_PLAIN returns performance to normal, but sadly most
users seem to have a preference for wavy error indicators.

One of the Geany team is looking at a more optimised implementation
(for the cairo implementation anyway) and will submit it if
successful.

Cheers
Lex

> --
> You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
> To post to this group, send email to scintilla-interest@googlegroups.com.
> To unsubscribe from this group, send email to scintilla-interest+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google