[Seaside-dev] Issue 116 in seaside: Improve profiler on Squeak

[codesite-noreply at google.com]

Comment #2 on issue 116 by renggli: Improve profiler on Squeak
http://code.google.com/p/seaside/issues/detail?id=116

I started to re-implement the code of the profiler tool. The most obvious  
change is that it possible to profile
during the callback phase and while processing AJAX callbacks. It does not  
show the profile result
immediately but collects many requests until the user hits the profile  
button again. One can inspect the
request and message send profile of the requests individually.

To get something more interactive like in GemStone the Squeak profiler  
itself needs to be updated (or re-
implemented). Currently the Squeak profiler is something that uses the most  
powerful class of the whole
image as a model. This class can be used to store anything and is very  
close to the underlying machine
architecture:  the String. Obviously for something like a profiler you need  
such an efficient solution ;-)

It would be cool if different profiles could be compared and remembered for  
later.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings