3 ms·

Perhaps they could invent a benchmarking tool that would allow them to write more efficient code that would utilize fewer resources on the server.

by 300bps 13y ago

VLM 13y ago
"There's been no suggestion that the benchmarks game website was the primary cause of that server load. It's just the result of the default configuration they use to provide dynamic content for 1,000 projects." If you wrote it, you'd have to get 999 other projects to bother to implement its results. What I would like to see rewritten is a (obvious) JVM view. So that's all very interesting that a n-body simulator in Clojure takes 60 times the memory and 4 times the exec time of a C version or about half a meg of ram per body in the n-body problem (uh, what?) What would really interest me is at a Debian OS level what is the delta when I move an identical benchmark from a Debian box running -i386 to -amd64 or at least for the interpreted JVM family of languages what happens to speed and memory when I move from vers 6 to vers 7 or how about alternative JVMs or whatever. More of an OS tweaking focus than a language focus. There is a startup lesson in this situation that anything shared can be a focus of pain, also any single point of failure can be a focus of pain. Not exactly new observations, but, still true. If instead of a benchmark site, this project was noobs trying to leverage the synergy of tweeting crowdsourced dog food delivery over the internet, they'd be dead meat once they disappear from search engines.
- igouy 13y ago
  >>What would really interest me ... vers 6 to vers 7<< All the measurements are in CVS so you actually could get at measurements for different versions. >>What would really interest me ... alternative JVMs<< Please take the program source code and the measurement scripts and publish your own measurements -- http://benchmarksgame.alioth.debian.org/play.php#languagex http://benchmarksgame.alioth.debian.org/play.php#languagex >>what is the delta when I move an identical benchmark from a Debian box running -i386 to -amd64<< Just open 2 web browsers and look ;-) http://benchmarksgame.alioth.debian.org/u64q/measurements.php?lang=clojure http://benchmarksgame.alioth.debian.org/u64q/measurements.ph... http://benchmarksgame.alioth.debian.org/u32q/measurements.php?lang=clojure http://benchmarksgame.alioth.debian.org/u32q/measurements.ph...
igouy 13y ago
That would not stop bots crawling the pages generated by the hosting software, about 90 pages for each of 1,000 projects, duplicated at 4 different sub-domains. This stuff -- http://alioth.debian.org/projects/benchmarksgame/ http://alioth.debian.org/projects/benchmarksgame/ The X-Robots-Tag HTTP header does provide a way for admins to instruct bots not to index and not to crawl -- without requiring changes to upstream software.

Perhaps they could invent a benchmarking tool that would allow them to write more efficient code that would utilize fewer resources on the server.

by 300bps 13y ago

Perhaps they could invent a benchmarking tool that would allow them to write more efficient code that would utilize fewer resources on the server.

VLM 13y ago

"There's been no suggestion that the benchmarks game website was the primary cause of that server load. It's just the result of the default configuration they use to provide dynamic content for 1,000 projects." If you wrote it, you'd have to get 999 other projects to bother to implement its results. What I would like to see rewritten is a (obvious) JVM view. So that's all very interesting that a n-body simulator in Clojure takes 60 times the memory and 4 times the exec time of a C version or about half a meg of ram per body in the n-body problem (uh, what?) What would really interest me is at a Debian OS level what is the delta when I move an identical benchmark from a Debian box running -i386 to -amd64 or at least for the interpreted JVM family of languages what happens to speed and memory when I move from vers 6 to vers 7 or how about alternative JVMs or whatever. More of an OS tweaking focus than a language focus. There is a startup lesson in this situation that anything shared can be a focus of pain, also any single point of failure can be a focus of pain. Not exactly new observations, but, still true. If instead of a benchmark site, this project was noobs trying to leverage the synergy of tweeting crowdsourced dog food delivery over the internet, they'd be dead meat once they disappear from search engines.

igouy 13y ago
>>What would really interest me ... vers 6 to vers 7<< All the measurements are in CVS so you actually could get at measurements for different versions. >>What would really interest me ... alternative JVMs<< Please take the program source code and the measurement scripts and publish your own measurements -- http://benchmarksgame.alioth.debian.org/play.php#languagex http://benchmarksgame.alioth.debian.org/play.php#languagex >>what is the delta when I move an identical benchmark from a Debian box running -i386 to -amd64<< Just open 2 web browsers and look ;-) http://benchmarksgame.alioth.debian.org/u64q/measurements.php?lang=clojure http://benchmarksgame.alioth.debian.org/u64q/measurements.ph... http://benchmarksgame.alioth.debian.org/u32q/measurements.php?lang=clojure http://benchmarksgame.alioth.debian.org/u32q/measurements.ph...

igouy 13y ago

That would not stop bots crawling the pages generated by the hosting software, about 90 pages for each of 1,000 projects, duplicated at 4 different sub-domains. This stuff -- http://alioth.debian.org/projects/benchmarksgame/ http://alioth.debian.org/projects/benchmarksgame/ The X-Robots-Tag HTTP header does provide a way for admins to instruct bots not to index and not to crawl -- without requiring changes to upstream software.