![]() Usually, if there are no issues here ol move onto gaming which will mostly be fine. Then I tend to run firestrike, watch for issues, monitor numbers and loads, same for time spy. Use heaven, for a first tier if it doesn't pass here, its fubar, same for if you notice any issues at all. Mind you, I've only been able to get some of the highest performance in the world out of my hardware over the past couple decades so I could be totally wrong. Personally I don't use torture tests, I run a suite of benchmarks and gaming to get real world numbers, a torture test is just that, the most extreme option possible and isn't really providing any real world numbers. Although I wouldn't want to exceed 80☌ because you never know when a thermalpad goes a bit bad and you might want some headroom. Often Core Temp can be 20☌ less than the temps measured on other sensors and in general you would not want to exceed 90☌ on any of them. GPU-Z might be an option but some manufacturers also got their own software to measure those different sensors. But never had any problems in the last step because in general its less power needed so might also be pointless its just what I do.Īnd you want to find a way to measure your not core GPU core temps. Tbh this is a bit tedious because you initially need to find those areas and those games (different engines are differently good in GPU utilization) and newer Games are not necessarily better in GPU utilization but if you got one or two of those games you are in general set and sound and your OC can handle evey game.Īfter that I would go for the 3d Mark and see how it handles those fluctuations. You can use Nvidia overlay to see voltage wattage and so on. I found a Lot of Games that pushed my GPU wattage more consistently to its limit than any sinthetic Benchmark. Part 4, the final part covers reliability testing the SD card storage - an unreliable filesystem makes the Pi unusable.I personaly would recommend Look for common OC's for your card and then go for demanding areas in different games. Using the Screen tool to create multiple virtual shells in which to run Memtester on multiple cores Running on multiple cores using several remote SSH shell confections Stress-testing the CPU with mprime (using all cores) In part 2 I look at stability testing in general, and introduce three tools. Tested Overclock Values – Failures and Successes Help! What To Do If The Pi No Longer Boots After Applying Overclock Changes ![]() Overclocking, Hardware Lifespan, and Your Raspberry Pi’s WarrantyĪ Note On Overclocking and SD Card StabilityĮditing Overclock Settings Within the Config.txt File ![]() Part Four: SD card storage reliability testing using the Stability Test Script single core testing and multicore running obtaining, installing and running mprime manually setting overclock parameters using config.txt The aim was to go beyond simply selecting an option in raspi-config and hoping for stability. I'm using a Pi 2 to run emulators using RetroPie, and have spent considerable time setting up and optimising the system, which lead me to write up some aspects of the process on a (non commercial) blog. Thoughts on Overclocking the Pi and Stability Testing: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |