On Wed, 10 May 2017, Matti Picus wrote:
It seems own tests are taking a very long time on this machine. I have
explored using jom.exe (https://github.com/qt-labs/jom) instead of nmake
to allow parallel compilation, which reduces my run of rpython's
translator\c\test\test_typed.py from ~700 secs to ~600 secs, where on
the same machine it is under 200 secs with linux. Note that the buildbot
requires over 2800 secs for the same test (see
http://buildbot.pypy.org/builders/own-win-x86-32/builds/1395/steps/shell_6/logs/stdio)
It is simply so that the machine kindly provided by the folks at Dartmouth
College where I migrated the Windows VM to is way slower than my old box,
and has only 2 physical cores in total...
Also take a note, that the same machine also does build & test runs for
git-annex, which take about an hour each, so that also doesn't speedup
PyPy builds.
Anyways, in the mean time, it looks like I've found colo in Germany for my
old machine, but I still need to:
* Get it shipped to the new datacenter
* Partly replace old hardware
* Install it & set it up anew
No ETAs, but something is moving in some direction at least. Getting
hardware is for now an unsolved problem though. I need 2 x 2/3 TB SATA
enterprise HDDs and 2 x enterprise SSDs + would be good to replace
unreliable DDR3 RAM sticks... Stuff that I have is 5 years old, and HDDs
tend to fail when they are old :-/
--
Sincerely yours,
Yury V. Zaytsev
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
