- Joined
- Oct 31, 2008
- Messages
- 1,332 (0.22/day)
- Location
- Portland, OR
| Processor | Ryzen 2600x |
|---|---|
| Motherboard | ASUS ROG Strix X470-F Gaming |
| Cooling | Noctua |
| Memory | G.SKILL Flare X Series 16GB DDR4 3466 |
| Video Card(s) | EVGA 980ti FTW |
| Storage | (OS)Samsung 950 Pro (512GB), (Data) WD Reds |
| Display(s) | 24" Dell UltraSharp U2412M |
| Case | Fractal Design Define R5 |
| Audio Device(s) | Sennheiser GAME ONE |
| Power Supply | EVGA SuperNOVA 650 P2 |
| Mouse | Mionix Castor |
| Keyboard | Deck Hassium Pro |
| Software | Windows 10 Pro x64 |
Wizzard,
It makes it more demanding of me to keep track of when I started the test and I don't see a launch time anywhere within the activity log. What is the best amount of loops that you have found to be 99% accurate?
I say that because I fully understand that the longer you run a program of this nature the better. I am just looking for a sweet spot that I can feel assured that there isn't memory related problems without running this for 24 hours on non-critical workstations.
It makes it more demanding of me to keep track of when I started the test and I don't see a launch time anywhere within the activity log. What is the best amount of loops that you have found to be 99% accurate?
I say that because I fully understand that the longer you run a program of this nature the better. I am just looking for a sweet spot that I can feel assured that there isn't memory related problems without running this for 24 hours on non-critical workstations.
