SqueakSource is down again

Philippe Marschall philippe.marschall at gmail.com
Sun Dec 23 11:14:17 UTC 2007


2007/12/23, Andreas Raab <andreas.raab at gmx.de>:
> Philippe Marschall wrote:
> > 2007/12/22, Rob Withers <reefedjib at yahoo.com>:
> >> This seems to be happening a lot.  Is there something that can be done to
> >> alleviate the problem?
> >
> > Yeah, fix the VM.
>
> What do you think is broken to cause those problems?

Basically the stuff that made you choose Gemstone over Squeak.
Semaphores for example (ok, not actually VW per se), other usual
suspects are the scheduler, Sockets and the GC. See the stack trace
Lukas sent earlier. Also it's not uncommon to have hundres of
processes hanging on the same Semaphore >> #critical:. The block has
terminated but the semaphore doesn't get released. I mean it's not
that we do something fancy like terminating a process. And sometimes
the image simply freezes and would stop reacting. An easy way to make
use of the second CPU sure wouldn't hurt as well.

Honestly I'm sick of searching which exact combination of what patches
I have to apply to which image and which GC tweaking I have to apply
to which VM with which patches collected from some posts or forks. Is
it asked to much that this stuff simply works?

Cheers
Philippe



More information about the Squeak-dev mailing list