Java/Timing: Difference between revisions
From charlesreid1
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
If you want an extremely detailed picture of how much time you're spending in the various parts of your code, you can use a profiler: see [[Java/Profiling]] | If you want an extremely detailed picture of how much time you're spending in the various parts of your code, you can use a profiler: see [[Java/Profiling]] | ||
==Basic Timing in Java: Builtin Methods== | |||
If you just want to see how much time a piece of code takes to execute, you can use Java's built in time functionality: | If you just want to see how much time a piece of code takes to execute, you can use Java's built in time functionality: | ||
| Line 10: | Line 12: | ||
System.out.printf("Elapsed time: %03f s\n", duration/1E9); | System.out.printf("Elapsed time: %03f s\n", duration/1E9); | ||
</pre> | </pre> | ||
==Timing Snippets of Code== | |||
Revision as of 11:34, 30 March 2017
If you want an extremely detailed picture of how much time you're spending in the various parts of your code, you can use a profiler: see Java/Profiling
Basic Timing in Java: Builtin Methods
If you just want to see how much time a piece of code takes to execute, you can use Java's built in time functionality:
long start = System.nanoTime();
doStuff();
long end = System.nanoTime();
long duration = end - start;
System.out.printf("Elapsed time: %03f s\n", duration/1E9);