Hi Phil, On 13 Feb 2013, at 18:39, "phil@highoctane.be" <phil@highoctane.be> wrote:
Don't know if this is related but the 2.0 image seems to runs slower on my box (20543 now).
That is hard to quantify, but any regressions should be investigated.
Also a question: why is there a ZnServer in the StartUpList ? I saw discussions on the loading of .changes if there is none in the image folder.
No, the automatic loading of .sources has become an option that is off by default. ZnServer is in the startup list, because it manages a list of registered server instances. If you create a ZnServer and it is registered, it will shutdown/restart on image shutdown/restart. This is something that is traditionally expected from servers running in a Smalltalk image. It can be handy during development, but I do not like it or use it for production systems. Sven
Phil
2013/2/13 Sven Van Caekenberghe <sven@stfx.eu>:
On 13 Feb 2013, at 18:17, "phil@highoctane.be" <phil@highoctane.be> wrote:
Is this related to that large list of [delaySemaphore wait] in Delay>>wait that I do see in the Process Browser? This thing wasn't so large in the past.
Let's hope so: it seems related, but we see it during startup (and subsequent crash) but also (sometimes) interactively in a working image.
Phil
2013/2/13 Igor Stasenko <siguctua@gmail.com>:
My personal take about this issue:
- when image starting up, all Delays should be reset by unblocking all waiting processes (regardless how much extra time there left to be waiting).
Because, to my opinion, a code which uses delays to cross session boundaries will fail badly anyways, so imo it is better to have delays unblocked the process prematurely, rather than blocking it for next 2^30 milliseconds (or any random big number around that).
-- Best regards, Igor Stasenko.