DOC PREVIEW
DREXEL CS 265 - In-class Timing Experiments

This preview shows page 1 out of 2 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 2 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 2 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

In-class Timing ExperimentsIn-class Timing Experiments Name: Download the C++ source code testing_timing.cpp from our course website. Compile and run the code in two environments: (i) Visual C++ on your PC: build a new empty workspace and place the C++ code inside it. (ii) Unix machine tux: Transfer the code to tux with SSH file transfer tool, compile and run it there. For each of the timing experiments you need to figure out first what is the number of repetitions needed for a numerically consistent outcome. In the next step you need to report the timing result you get, and then express in nanoseconds the average time spent on an indicated operation. Make sure to review the website on time units: http://en.wikipedia.org/wiki/Orders_of_magnitude_(time) prior to starting your work. All operations should be applied to integer type arguments. (i) Review the code testing_timing.cpp in detatil and explain the essence of the timing experiment:(ii) PC operation + reported consistent timing output: average operation time converted to nanoseconds: operation - reported consistent timing output: average operation time converted to nanoseconds: operation * reported consistent timing output: average operation time converted to nanoseconds: operation / reported consistent timing output: average operation time converted to nanoseconds: operation % reported consistent timing output: average operation time converted to nanoseconds: (iii) tux operation + reported consistent timing output: average operation time converted to nanoseconds: operation - reported consistent timing output: average operation time converted to nanoseconds: operation * reported consistent timing output: average operation time converted to nanoseconds: operation / reported consistent timing output: average operation time converted to nanoseconds: operation % reported consistent timing output: average operation time converted to


View Full Document

DREXEL CS 265 - In-class Timing Experiments

Download In-class Timing Experiments
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view In-class Timing Experiments and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view In-class Timing Experiments 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?