From: Austin Ziegler Date: 2006-09-15T21:11:55+09:00 Subject: Re: Benchmark for Ruby On 9/14/06, M. Edward (Ed) Borasky wrote: > Once you know where Ruby is spending its time, play with compiler flags. > gcc has oodles of possible optimizations, and gcc itself was tuned by > processes like this. It's worth spending a lot of time compiling the > Ruby interpreter, since it's going to be run often. Playing with compiler flags is of limited utility across the board. The compiler flags for each platform *will* *differ*, and GCC optimizations are different than native compiler optimizations (and GCC isn't well-optimized off PPC and Intel; I will never compile something with a non-native compiler if I can avoid it for any reason). I'm not interested in things that require compiler flag tweaks -- that's far too variant and should be done on a per-system basis. I'm looking for a benchmark suite that show areas where the implementation can be improved. I'm not looking for artificially limited benchmarks where a simple tweak of an operating system option (e.g., ulimit) enables the benchmark to run or run faster. There's the difference. -austin -- Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/ * austin@halostatue.ca * http://www.halostatue.ca/feed/ * austin@zieglers.ca