[code] Profiling Lua

From: Brian Schott <briancschott.att.gmail.com>
Date: Thu, 19 Apr 2012 11:34:49 -0700

Textadept claims to be "relentlessly optimized for speed", but it
seems to die a terrible death when opening this file:

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)

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 Thu 19 Apr 2012 - 14:34:49 EDT

This archive was generated by hypermail 2.2.0 : Fri 20 Apr 2012 - 06:32:13 EDT