|
From: Peter J. <pet...@gm...> - 2012-02-27 10:44:30
|
2012/2/27 Bastian Märkisch <bma...@we...>: >>>> I've fired up that virtual machine that produced that 5 minute delay >>>> earlier. Some observations on several different builds: >>>> >>>> gp46rc1-win32-setup.exe from http://gnuplot.info/development/binaries/ >>>> (25-Feb-2012 07:19): a small (1-2 s) delay on startup. >>>> >>>> gp450win32-small-setup.zip from >>>> http://www.tatsuromatsuoka.com/gnuplot/Eng/winbin/ (2012-02-23, md5sum >>>> feebe279501075f8806a04a4029f899c): No delay at all! >>>> >>>> gp450win32-setup.zip from the same location (2012-02-23, md5sum >>>> 728918c93811f1644711c05fecaebd8f): several minutes of delay. >>>> >>>> I thought that if the delay is related to the initialization of the wxt >>>> terminal, then setting the GNUTERM variable to "windows" may alleviate >>>> the problem, but it didn't. >>>> >>>> Péter Juhász >>>> >>> One of the possibility is that the version of wxwidgets. Now I am using >>> wxwidgets-2.9.3. >>> To be clear I have to rebuiild wxwidigts 2.8 and re-provide the binary. >>> Now my condition is not so good, I cannot commit further at the moment. >>> >>> Sorry for inconvenience. >>> >>> Tatsuro >>> >> >> Hello >> >> I have downgraded wxWidgets from version 2.9.3 to 2.8.12 and built the >> recent cvs source. >> http://www.tatsuromatsuoka.com/gnuplot/Eng/winbin/ >> gp450win32-setup.zip >> >> Please test this binary shows slow startup or not. >> >> Regards >> >> Tatsuro >> > > Thanks for providing a new build so quickly! On my Vista machine your (old) > build with wxWidgets 2.9.3 takes ~6s to start up, whereas the build with > wxWidgets 2.8.12 takes only 0.7s. This is exactly the same time it takes for > my own build to start up (wxWidgets 2.8.11). > For the moment, I would thus suggest to stay with 2.8 for a 4.6 release > build. > > Bastian I confirm the speedup with this new build: on this pathological Vista virtual machine I have the delay on startup has shrunk down to 8 seconds. On a real XP box the delay is less than 1 s. Perhaps it would be illuminating to look at the changelogs of wxWidgets to see what could possibly cause this effect, and also test whether it appears on non-Windows platforms. Péter Juhász |