Where to look for performance issues

Hi Neil and ScintillaGTK experts,

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.

The file used is just a 500 line Python file, ie nothing special.

We have upgraded Geany to Scintilla 3.2 with no effect.

As we have no expertise in the internals of ScintillaGTK and as it
takes all day for the problem to be reliably visible it is very slow
going trying to find anything.

Can Neil or anyone suggest the most likely places to look and what
methods might be safely used without upsetting the operation of
Scintilla (at the moment we just use a timer and print the time to the
output but that would probably make the whole thing unusable if it was
inside some of the functions that are called millions of times)

Note that profiling isn't useful as it takes so long for the problem
to be visible that all the profiling counters have wrapped around
several times and so the data is meaningless.

Current test bed is Linux XFCE4 with GTK 3.24.10 Glib 2.30.2.

Thanks
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 <at> googlegroups.com.
To unsubscribe from this group, send email to scintilla-interest+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.