Hi all, Before shooting the messenger of bad news let we rather acknowledge that there are problems in Squeak/Pharo on the socket/semaphore/process field. I also admit, I somewhat lost nervers on Pharo as Guido did and I'd like to post the same post. But of course bringing bad messages must always be done diplomatically of you won't like to be shoot :)
So, known problems are: socket limit over about 200, semaphores (i remember discussion back, is this solved?) protecting critical sections doesn't work well, processes? So Guido is right, don't shut them, let his anger rather energitize us to finally solve them! Janko S, Stéphane Ducasse piše: > Sven from beta9 is using Pharo as a server and it works well from what he > told us during the last sprint. > Netstyle is also using pharo for Seaside. > > Now there is certainly place for improvements and pharo is improving every > day (but because there are cool pharoers improving it). > > I noticed in the past that you always have this same aggressive tone. > And even worse, we value critics and non politically correct discussions but > not systematic bashing. > What I dislike is the tone of your email. So do not continue like that if you > want to have any support for people. > else you will be plonkified :) > >> I am doing server tuning, building up fast server systems for a very long >> time now. >> >> Yesterday i installed 1.2.1, expecting to see a far more matured Pharo >> Smalltalk, stable, pretty nice new features. >> >> I opened up the Memory Grapher, hmmm.... works fine, watching memory >> pumping. A bit strange, seeing a Pharo consuming and freeing megabytes of >> memory space without any load. But ok! >> >> Then i opened up TestSuites, marked some tests, let them run. Ups! Desktop >> hanging. >> >> I expected to have with Pharo a well done, stable multitasking environment, >> but Pharo hangs everywhere, is leaking lots of memory, is keeping up >> connections, wasting resources unneccessarily, having problems with internal >> race conditions on semaphores, mutexes, feels same like "Big Kernel Lock", >> but even without MultiProcessing. > > Only that. Not bad. We are soo dumb that it could be so worse. > >> The Pharo Team IMHO is very much missing important knowledge about modern >> Operating System Design, what Pharo Smalltalk OS is in fact, without being >> able to fulfill the minimum standards i expect from a usable Smalltalk OS. >> >> As system operator or enterprise i cannot offer such a system, that has to >> be restarted twenty times a day, due to hangs, memory leaks, sucking >> connection handles, ..., whatever! >> >> tnx for your understanding! > > My understanding is that you do not know how to communicate. > > Now my advice is to try 1.3 because lot of improvements were applied and for > example Zinc is a good starting part. > >> >> regards, Guido Stepken > > > -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
