Re: [code] Profiling Lua

From: Mitchell <m.att.foicica.com>
Date: Sun, 22 Apr 2012 14:16:58 -0400 (EDT)

Brian,

On Thu, 19 Apr 2012, Brian Schott wrote:

> More information:
>
> 2) The file still takes nearly 10 seconds to load. SciTE loads this
> instantly. Removing the D entry from mime_types.conf causes the file
> to be loaded in roughly 23 seconds. This is very strange, as I thought
> that the container lexer was supposed to be the fastest since it
> doesn't do anything.

SciTE has some fancy asychronous loading going on for the last new
releases so maybe that's the explanation? Try loading your file with an
older release and let me know if it's still the same.

> 3) Things as simple as cursor movement have significant lag when the
> lexer is set to "container" and the cursor is near the bottom of the
> file. Placing the cursor near the top of the file OR setting the lexer
> back to D brings the speed back to what is expected (i.e. instant).

I will investigate this. Thanks for bringing it up.

Mitchell

>
> On Thu, Apr 19, 2012 at 12:17 PM, Mitchell <m.att.foicica.com> wrote:
>> Brian,
>>
>>
>> On Thu, 19 Apr 2012, Brian Schott wrote:
>>
>>> Textadept claims to be "relentlessly optimized for speed", but it
>>> seems to die a terrible death when opening this file:
>>> https://raw.github.com/D-Programming-Language/phobos/master/std/datetime.d
>>
>>
>> Other than taking some time to load, it works for me. Editing is still
>> snappy too. Peak memory usage is under 80MB.
>>
>>
>>> What's the best way of profiling the lua code so that I can hopefully
>>> fix TA for large files? (Before anyone mentions Scintilla as a cause
>>> of the speed problem, load that file in SciTE.) Callgrind is fairly
>>> useless at profiling Lua code. (Also, it took several minutes for TA
>>> to open that file when being run in Valgrind)
>>
>>
>> I remember you had a problem with an HTML file some time ago and the way I
>> found out what caused the problem was to bisect the file to find the chunk
>> that was causing the slowdown.
>>
>> 9 times out of 10 it's an LPeg parsing issue so I'm not sure what can be
>> done except finding the chunk of text the editor is choking on.
>>
>> Mitchell
>> --
>> You are subscribed to code.att.foicica.com.
>> To change subscription settings, send an e-mail to code+help.att.foicica.com.
>> To unsubscribe, send an e-mail to code+unsubscribe.att.foicica.com.
>>
>

Mitchell

-- 
You are subscribed to code.att.foicica.com.
To change subscription settings, send an e-mail to code+help.att.foicica.com.
To unsubscribe, send an e-mail to code+unsubscribe.att.foicica.com.
Received on Sun 22 Apr 2012 - 14:16:58 EDT

This archive was generated by hypermail 2.2.0 : Mon 23 Apr 2012 - 06:31:23 EDT