[Seaside] Re: [Glass] adding profiling to GemStone
Dale K. Henrichs
dale.henrichs at gemtalksystems.com
Sat Jan 4 16:55:23 UTC 2014
I will try to look into the profiler issues for GemStone ... I'm not familiar with the Seaside Profiler code ... I wrote a nice profiler for Seasdie3.8 way back when, but that work never got ported to Seaside3.0 ...
----- Original Message -----
| From: "Otto Behrens" <otto at finworks.biz>
| To: glass at lists.gemtalksystems.com, "Seaside - general discussion" <seaside at lists.squeakfoundation.org>
| Sent: Tuesday, December 31, 2013 6:03:17 AM
| Subject: [Glass] adding profiling to GemStone
| I want to reuse the current Seaside-Pharo-Development-Core-Profiler
| classes in GemStone. So I moved the general classes to
| Seaside-Development-Core-Profiler and created a hook that implements
| Pharo and GemStone specific profiling in
| Seaside-Pharo-Development-Core-Profiler and
| Seaside-GemStone-Core-Profiler respectively.
| I made some changes in Seaside-Development and
| Seaside-Pharo-Development here:
| Is this change helpful for Seaside?
| The GemStone version is simplistic at the moment; I'm really battling
| to get it to work in GemStone. My problem is that the block being
| profiled does not return; the response notification seem to block in
| GemStone and does not return in #handleFiltered:. I would like to
| incorporate ProfMonitor, but I'm not even getting as far as measuring
| the time it took to execute #handleFiltered:.
| Does anyone have an idea how I can profile seaside requests in
| Glass mailing list
| Glass at lists.gemtalksystems.com
More information about the seaside