On Apr 12, 2010, at 10:18 PM, Facundo Vozzi wrote: > Stef, > I'm using Pharo 1.0 RC2 with Seaside 2.8.4 and all is fine but it took over > 15 seconds open a smalltalk debugger from a Seaside wallback. It was the > reason of my first mail. > I tried with Squeak 4.1 RC4, to discard a network configuration problem at > operative system level, and i don't have the problem. It takes 1 second to > open the debugger. > Then, Marcus ask to me if i had the same problem with > "PharoCore-1.1-11301-UNSTABLE", at that time I download it, installed Seaside > and try again. To Install Seaside took to me over 20 minutes but I had been > instaled it on Pharo 1.0 and was been fine.
ok so with 1.1 this is working? There were a **lot** of changes in 1.1. We will release shortly after 1.0 and much much faster :) > Is it more clear now ?. Please, sorry for my poor English. Don;t worry. write simple sentences and we will understand you. > > Facu > > > On Mon, Apr 12, 2010 at 5:03 PM, Stéphane Ducasse <[email protected]> > wrote: > This is really strange. Can you describe your setup? Do you have an > antivirus? And with Squeak you do not have that behavior? > We are loading larger code than seaside in Pharo and we do not have this > problem. > So I would really like to understand. Could you post your image somewhere? > > Stef > > On Apr 12, 2010, at 9:27 PM, Facundo Vozzi wrote: > > > Stef, > > It took to me over 20 minutes to complete the Seaside 2.8 installation and > > when I interrupted it the debugger opened when the system was writting the > > pharoXXX.changes always but I couldn't check what is happening. > > > > I will check it again. > > > > Facu > > > > ps: I refered to pharoXXX.changes as "log" because of Visual Smalltalk > > where the "changes" are called changes.log, excuse me. > > > > On Mon, Apr 12, 2010 at 3:05 PM, Stéphane Ducasse > > <[email protected]> wrote: > > > > On Apr 12, 2010, at 7:45 PM, Facundo Vozzi wrote: > > > > > Marcus, > > > I can't install Seaside on Pharo 1.1(*) but then i'll try again at home. > > > > > > It isn't my point to compare Pharo to Squeak performance but I used > > > Squeak to test this particular situation. > > > > > > Thank you, > > > > > > Facu > > > > > > (*) it's very slow to write the log taking minutes to complete the > > > instalation > > > > which log? > > > > Stef > > > > > > > > On Mon, Apr 12, 2010 at 12:54 PM, Marcus Denker <[email protected]> > > > wrote: > > > > > > On Apr 12, 2010, at 5:41 PM, Marcus Denker wrote: > > > > > > > > > > > On Apr 12, 2010, at 5:37 PM, Facundo Vozzi wrote: > > > > > > > >> Lukas, > > > >> It happens on my machine with Windows/(Firefox-Chrome-IE 8) and Pharo. > > > >> > > > >> But I test it on the same machine with Squeak 4.1 RC4 and it go very > > > >> very fast > > > >> to open de smalltalk debugger. > > > >> Furthermore, Squeak 4.1 RC4 seem to be faster than Pharo, did you note > > > >> that too or it's only my sensations? > > > >> > > > > > > > > Did you check with Pharo 1.1? > > > > > > > > > > > > https://gforge.inria.fr/frs/download.php/26762/PharoCore-1.1-11301-UNSTABLE.1.zip > > > > > > > > In general, Squeak 4.1 should not be compared to Pharo 1.0 speed-wise, > > > > but Pharo 1.1 > > > > > > > > > > My theory for your bug is that it's this: > > > > > > http://code.google.com/p/pharo/issues/detail?id=860 > > > > > > We added it to 1.1 on Nov. 01, 2009. Not to 1.0, because 1.0 was supposed > > > to be released > > > "very soon". > > > > > > Marcus > > > > > > > > > > > > -- > > > Marcus Denker -- http://www.marcusdenker.de > > > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > [email protected] > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > > > -- > > > Facundo Vozzi > > > InfOil S.A. > > > Project Leader > > > (+54-11) 4542-9999 x108 > > > [email protected] > > > _______________________________________________ > > > Pharo-project mailing list > > > [email protected] > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > [email protected] > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > > Facundo Vozzi > > InfOil S.A. > > Project Leader > > (+54-11) 4542-9999 x108 > > [email protected] > > _______________________________________________ > > Pharo-project mailing list > > [email protected] > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > Facundo Vozzi > InfOil S.A. > Project Leader > (+54-11) 4542-9999 x108 > [email protected] > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
