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.

Sign up for GitHub

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

Jump to bottom

dc benchmark much too short #8

Open

GoogleCodeExporter opened this issue Apr 9, 2015 · 0 comments

Labels

auto-migrated Priority-Medium Type-Defect

GoogleCodeExporter commented Apr 9, 2015

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 [email protected] on 7 Nov 2012 at 6:53

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Priority-Medium Type-Defect auto-migrated labels

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