[Seaside] Re: [Glass] adding profiling to GemStone

Dale K. Henrichs dale.henrichs at gemtalksystems.com
Sun Jan 5 20:52:52 UTC 2014

----- Original Message -----
| From: "Otto Behrens" <otto at finworks.biz>
| To: "Dale K. Henrichs" <dale.henrichs at gemtalksystems.com>
| Cc: glass at lists.gemtalksystems.com, "Seaside - general discussion" <seaside at lists.squeakfoundation.org>
| Sent: Sunday, January 5, 2014 12:15:32 PM
| Subject: Re: [Glass] adding profiling to GemStone
| > I created a pull request[1] that fixes the problems that I ran into
| > with this code.
| >
| > I "fixed the problem with the profiled block not returning" by
| > putting in an ensure block ... AFAIK, when one is working with
| > #handleFiltered:, the code that follows the block does not get
| > executed because continuations are getting created and normal
| > block execution does not apply ... I looked at the other filter
| > tools and it looks like they were all using ensure blocks to
| > perform work "after block execution" and that grick worked for
| > WAProfilerItem>>profile too.
| Thanks, Dale. I can do more with the profile now.

I'm pretty familiar with the gory details of the GemStone profiler, if you want some more help...

| > I haven't done anything more with the profile, but it is tempting
| > to port the Seaside2.8 code to Seaside3.0, since I'm in the
| > neighborhood:)
| Are you talking about glassdb/Seaside30? Is there some porting work
| to
| be done in here? Perhaps it's worth it to go for Seaside 3.1. Let me
| know where I can help.

I was thinking glassdb/Seaside30 since that's where you're doing the current profiling work...


More information about the seaside mailing list