Message6083

Author pekka.klarck
Recipients fwierzbicki, pekka.klarck, pjenvey, yanne, zyasoft
Date 2010-09-20.20:08:09
SpamBayes Score 5.34688e-08
Marked as misclassified No
Message-id <1285013290.08.0.941502262107.issue1380@psf.upfronthosting.co.za>
In-reply-to
Content
I just tested the start-up time of 2.5.2b2 on Linux and Windows XP (different machines). I got both good and bad news, let's start with the former.

On Linux the start-up time has improved, but is still quite far away from 2.2. Running the same command as yanne in the original report gives these results:

2.5.2 beta 2:
real	0m53.332s
user	1m6.652s
sys	0m5.136s

2.5.1:
real	1m5.767s
user	1m35.698s
sys	0m6.288s

2.2:
real	0m28.580s
user	0m35.582s
sys	0m2.440s

The bad news is that on Windows the start-up time has gotten worse. I created a simple Python script to run similar test as on Linux. The average start-up time was 1.94s with 2.5.1 and 2.58s with 2.5.2b2. I don't have 2.2 installed on this machine.

Could the new start-up time regression on Windows be related to the recent jython.bat fixes? It was great to see that the problems we had reported are fixed (#1567 and #1599) but start-up time getting worse isn't so nice. Could the native Windows launcher (#1491) improve the situation?
History
Date User Action Args
2010-09-20 20:08:10pekka.klarcksetmessageid: <1285013290.08.0.941502262107.issue1380@psf.upfronthosting.co.za>
2010-09-20 20:08:10pekka.klarcksetrecipients: + pekka.klarck, fwierzbicki, pjenvey, zyasoft, yanne
2010-09-20 20:08:10pekka.klarcklinkissue1380 messages
2010-09-20 20:08:09pekka.klarckcreate