Jean-Baptiste BRIAUD -- Novlog wrote: > I guess build time is consumed by disk IO so compile the Python build > won't change that ...
here are some benchmarks in a 407-class project. it's a 2 something ghz laptop, with cpufreq governor = performance. running off ram, no cache: $ time python generate.py build (...) real 3m23.815s user 3m21.282s sys 0m2.230s just 2 seconds for io, that's as fast as it'll get w/o psyco. running off ram, with cache: real 0m7.719s user 0m4.977s sys 0m1.087s and this is as fast as it'll get with a cache, w/o psyco. running off disk, no cache, invalidated io buffers: real 10m25.108s user 2m59.202s sys 0m7.185s a whopping seven and a half minutes spent doing disk io. note that my disk is particularly slow, as it's an encrypted partition. running off disk, with cache, invalidated io buffers: real 4m1.299s user 0m6.989s sys 0m2.546s so using the cache saves less than half the disk io, and almost all cpu-intensive tasks. i guess your best option is to run your builds off ram. psyco won't help you, it's the toolkit developer's job to integrate it. benchmarks show that even if they did, there wouldn't be much difference. best, burak ps: here are some relevant info: http://stackoverflow.com/questions/556405/what-do-real-user-and-sys-mean-in-the-output-of-time1 http://forum.soft32.com/linux/invalidate-drop-filesystem-caches-io-buffers-ftopict335297.html ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
