from what I remember runsnakerun has the entire call stack. It's not hard
to identify where is the bottleneck. BTW: a read() such as in socket.read()
is hardly something that needs fixing.
On Friday, June 12, 2015 at 7:11:44 AM UTC+2, mweissen wrote:
A second question:
I have found that a
On Thursday, June 11, 2015 at 11:29:01 PM UTC-7, Niphlod wrote:
from what I remember runsnakerun has the entire call stack. It's not hard
to identify where is the bottleneck.
The cprofilev tool in the OP also allows drilling down; the default view
shows all levels, but by clicking on
runsnakerun is the best tool for the job.
for running with profiler and another webserver, you need to tweak
wsgihandler.py pass a directory to profiler_dir
On Thursday, June 11, 2015 at 8:39:45 PM UTC+2, mweissen wrote:
I have tried the option -F with a simple web2py start:
python
Thank you very much for your fast response.
2015-06-11 21:15 GMT+02:00 Niphlod niph...@gmail.com:
runsnakerun is the best tool for the job.
for running with profiler and another webserver, you need to tweak
wsgihandler.py pass a directory to profiler_dir
On Thursday, June 11, 2015 at
A second question:
I have found that a read-command consumes a lot of time. All other
statements are not conspicuous.
ncalls tottime percall cumtime percall filename:lineno(function)
12.9392.9392.9392.939 {built-in method read}
15.0805.0805.0805.080
5 matches
Mail list logo
