[Glass] adding profiling to GemStone

Philippe Marschall philippe.marschall at gmail.com
Thu Jan 2 04:17:02 PST 2014

On Tue, Dec 31, 2013 at 3:03 PM, Otto Behrens <otto at finworks.biz> wrote:
> Hi,
> I want to reuse the current Seaside-Pharo-Development-Core-Profiler
> classes in GemStone.

I believe I saw a profiler one but maybe my memory is playing tricks with me.

> 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: https://github.com/finworks/Seaside30.
> Is this change helpful for Seaside?

Yes, once you have a running version and know which hooks you need.

> 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 GemStone?


More information about the Glass mailing list