10000 dc benchmark much too short · Issue #8 · kdlucas/byte-unixbench · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

dc benchmark much too short #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
A118
GoogleCodeExporter opened this issue May 7, 2015 · 0 comments
Open

dc benchmark much too short #8

GoogleCodeExporter opened this issue May 7, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link
What steps will reproduce the problem?
1. Running the dc benchmark

The command dc < dc.dat is computed very fast on modern computers, less than a 
millisecond. So the dc benchmark is benchmarking fork and exec instead 
(looper.c).

It is easy to change, by increasing the precision of sqrt(2) calculation.

Thanks

Original issue reported on code.google.com by sco...@googlemail.com on 7 Nov 2012 at 6:53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0