User:RhythmicDaze

Short Bio
Hello! I'm a post-college student who spends his days at home building/repairing computers and game consoles, eating yummy cookie dough, reading up on all things tech-enthusiast worthy, and tweaking/modding my devices to the max!

As for my part in the community, I have recently started helping out with editing the Hardware performance page. Mainly, I make corrections and add in missing information so that users can make proper comparisons between their hardware and user-posted results. It's my first for Wiki editing, though I do it for the greater good of users who view results and don't want to be confused by certain mistakes they may come across.

I make editing mistakes too. In that case, if you have tips for future editing based on previous edits I have made, please let me know through my talk page, User talk:Bb 20, or through an email.

~Thanks for visiting my humble profile, and have a great day!~

Intro
I have always been interested in tweaking software to have it work faster for me. Overclocking, Windows registry editing, optimization utilities, ect... Those are the types of things that I like to play around with. This nice thing about the Nvidia Control Panel is that you can have profiles per executable that contain different options for how the graphics drivers work with that program. Here, I will show you some of the effects of these profile options when coupled with javaw.exe.

Testing Methodology
Currently, I am using Java JRE 8 to do these tests. However, performance is very similar to that of Java SE 7 Update 40. Also, Fraps is being used to collect these figures. The reason for this is that when you have the debuging overlay enabled while in-game, your FPS drops by a good few percent, a lot of times for me it drops by ~100FPS!

With Debug Screen Frames: 78889 - Time: 120000ms - Avg: 657.408 - Min: 590 - Max: 686

Without Debug Screen Frames: 95007 - Time: 120000ms - Avg: 791.725 - Min: 740 - Max: 809

If we calculate the percent difference between the average number of frame for both of these results...

((x/y)*100)-100 ((657/791)*100)-100 = -17.04...

...we come out with a 17% FPS difference! I call that a hit, folks.

Results
NOTE: Each test below was recorded within 60 second period.

Java 7, Fullscreen Frames: 32193 - Time: 60000ms - Avg: 536.550 - Min: 476 - Max: 617

Java 8, Windowed Frames: 84912 - Time: 120000ms - Avg: 707.600 - Min: 552 - Max: 842

Java 8, Fullscreen Frames: 63836 - Time: 120000ms - Avg: 531.967 - Min: 486 - Max: 616

NOTE: Each test below was recorded within 120 second period.

Frames: 76549 - Time: 120000ms - Avg: 637.908 - Min: 578 - Max: 676

Max pre-rendered = 1, Alt Frame Rendering 2, High Performance, Thread Optimization = OFF Frames: 92154 - Time: 120000ms - Avg: 767.950 - Min: 692 - Max: 795

Max pre-rendered = 4, Alt Frame Rendering 2, High Performance, Thread Optimization = ON Frames: 74193 - Time: 120000ms - Avg: 618.275 - Min: 547 - Max: 651 Frames: 73982 - Time: 120000ms - Avg: 616.517 - Min: 500 - Max: 654

Max pre-rendered = 4, Alt Frame Rendering 2, High Performance, Thread Optimization = OFF Frames: 90407 - Time: 120000ms - Avg: 753.392 - Min: 656 - Max: 807

Max pre-rendered = 4, Alt Frame Rendering 1, High Performance, Thread Optimization = OFF Frames: 93960 - Time: 120000ms - Avg: 783.000 - Min: 688 - Max: 808

Max pre-rendered = 4, Single GPU, High Performance, Thread Optimization = OFF Frames: 95006 - Time: 120000ms - Avg: 791.717 - Min: 708 - Max: 814

Best Settings
Max pre-renderded frames = ?, Multi-display/mixed GPU acceleration = ?, Power management mode = ?, SLI rendering mode = ?, Thread optimization = ?, [other option here?] = ?.

These combination of settings above should give the player the best performance overall.

Conclusion
Changing Nvidia Control Panel options is something you will want to look into if you want to squeeze more performance out of your machine. This is great for if you can't immediately upgrade your hardware components, overclock or if your machine can't be upgraded for that matter.