From: <bc...@wo...> - 2001-12-12 10:31:08
|
[Jan Wender] >I removed the cachedir and started each jython version two times, and there are >large differences between the first and second startup and not so large between >2.1a3 and 2.1b1. Thanks. Now I'm convinced that the jar cache isn't the problem in your case. Then try something like this. Notice the -S option. >jython-2.1a3-jdk13\jython -S -c "from time import time; t = time(); import site; print time() - t" 0.11000001430511475 >jython-2.1b1-jdk13\jython -S -c "from time import time; t = time(); import site; print time() - t" 0.44099998474121094 >jython-2.1a3-jdk13\jython -S -c "from time import time; t = time(); import re; print time() - t" 0.24000000953674316 >jython-2.1b1-jdk13\jython -S -c "from time import time; t = time(); import re; print time() - t" 0.25099992752075195 >jython-2.1a3-jdk13\jython -S -c "from time import time; t = time(); import os; os.sep; print time() - t" 0.04999995231628418 >jython-2.1b1-jdk13\jython -S -c "from time import time; t = time(); import os; os.sep; print time() - t" 0.3500000238418579 I use time.time() to do the timing, but that might only make sense for win2k. Keep using the shell time command for *nix. Make sure you run each command a couple of times to avoid disk cache artifacts. The slowdown that I can measure is consistent with the use of "re" in "os". >Would it help if I tried different Java VMs? Let's stick with what we have for now. >I hope this helps, I really want to find the cause of this slowdown. Me too. regards, finn |