ATTENTION! Do not include the the time of print_tally in your analysis or optimizations Hand-in:
- Documentation of the current performance of the program, including why you believe your performance measurements are free of errors.
- An explanation of the bottlenecks in the program.
- A hypothesis of what is causing the problem, and a changed program which is improved to solve the problem.
- Documentation of the new performance, again including documentation that the measurements are free of errors.
- Notice: there might be more than one optimization needed to achieve optimal performance.
- Clone project to your computer
- Open the word .doc ("Perfromance Assignment dokumentation") and read it.
- Open up the project file in a Java IDE of you choosing
- Now to get the location of you file "" on your computer. open up the folder, Go "src --> resources --> resources. No copy paste the path including the filename and .txt at the end e.g. My path is: C:\Users\Jonas\Documents\GitHub\Code-Performance_letter-frequencies\Project\src\main\resources\FoundationSeries.txt
- Paste the path into the main method inside of the project.
- Run any of the 3 methods and compare your result the the excel ark ("excel of performance Pre & after modification") with this repo, to see a comparason between how much hardware effect the result.