This site is awful when it comes to everything DPC, and considering that's the main attraction here I feel vindicated in being harsh about this. This entire website is objectively misinformation when it comes to DPC, but I'll explain why so people can learn:
1) The testing methodology is terrible here. Every single LatencyMon test MUST be ran for exactly the same amount of time or you CANNOT rightfully compare one computer to another. This is basic troubleshooting and benchmarking 101 information, eliminate the variables. In other words, every test should be 5 minutes, not a minute more or less.
2) This site sorts the tables according to the highest SPIKE in DPC, which is not at all indicative of overall performance. Yes, spikes matter, but what matters far MORE is the AVERAGE DPC latency which is on a different tab in LatencyMon than what the owner's constantly post screenshots of. That is how the tables should be sorted, and this information is more critical than the spikes.
3) Another huge testing methodology flaw is there is way, way, way too much crap running on these computers, evident in the task manager. Handles over 100,000 ROFL, good grief. ALL tests must be performed on a CLEAN install of Windows, without ANY drivers installed. That's how you get a baseline for the HARDWARE. Or you could ONLY install the required drivers (no optional drivers or other bloat) and then record that data.
4) ALL tests must be done on exactly the same build of Windows. You also must not have an active internet connection because the background processes in Windows will use this and interfere with the benchmarking. This is again, basic benchmarking 101 information. You also do not test DPC latency by opening up a browser, playing videos, etcetera, because that has way too many variables. Idling at the desktop with or without drivers is really all you need, don't overcomplicate it because once you start running other software like a browser you then add a ton of variables, such as coding that might not play nice with very specific hardware or drivers, etcetera. That's why we just record data while idle at the desktop. In addition, always perform a reboot before benchmarking, then wait 5 minutes before starting to record so the bulk of the background activity can die down.
There's more I can get into, but clearly there is more wrong on this site regarding DPC than there is correct. All of these DPC tests are completely invalid and cannot be used at all to compare one laptop to another. It's completely inaccurate, I cannot stress just how bad the tests here are. I've made this comment on both the lowest and highest DPC laptops to help get this information seen so the viewers know that the most important aspect of this site isn't valid, and hopefully the owners will not knee-jerk at me, and instead take this constructive criticism to heart and fix their site.