4 ms·
> writing to stdout rtm "with output redirected to /dev/null" ! https://benchmarksgame-team.pages.debian.net/benchmarksgame/how-programs-are-measured.html#mea
by igouy 8y ago
> writing to stdout
rtm "with output redirected to /dev/null" !
https://benchmarksgame-team.pages.debian.net/benchmarksgame/how-programs-are-measured.html#measured https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
> new BufferedOutputStream(System.out);
$ time /opt/src/jdk-10.0.1/bin/java mandelbrot 16000 > /dev/null
real 0m7.144s
user 0m27.405s
sys 0m0.156s
> new FileOutputStream("./mandel_out")
$ time /opt/src/jdk-10.0.1/bin/java mandelbrot 16000
real 0m7.125s
user 0m27.367s
sys 0m0.184s
- sorokod 8y agoYup - writing to disk it pretty fast. Not sure what your point is though as according to https://benchmarksgame-team.pages.debian.net/benchmarksgame/program/mandelbrot-java-2.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... the output for the benchmark is not redirected to /dev/null : COMMAND LINE: /opt/src/jdk-10.0.1/bin/java mandelbrot 16000
- igouy 8y agortm "2. If the program gives the expected output within an arbitrary cutoff time (120 seconds) the program is measured again (5 more times) with output redirected to /dev/null."
- igouy 8y agortm "1. Each program is run and measured at the smallest input value, program output redirected to a file and compared to expected output. As long as the output matches expected output, the program is then run and measured at the next larger input value until measurements have been made at every input value."