Poll: What Machine To Purchase For Review

[FaunCB]

Also I want to note here that, though some reviews said that at load the battery life was anywhere from 3-5 hours, on battery I’ll at most be doing web and text documents, and seeing the notebookcheck review it says 426 minutes, or 7.1 hours.

I’m not worried at this point. The votes appear to have slowed so I may just close the poll now. Or in the morning maybe.

If you guys have specific tests from my list of stupid / ridiculous benchmarks that you want me to do, or specific things to check out, let me know. I’m going with a 16GB Ram, 512GB SSD, 1TB HDD model. I might bump to the 32GB if I need to.

Link to the article in question: https://www.notebookcheck.net/HP-Envy-x360-15z-Ryzen-5-2500U-Vega-8-SSD-FHD-Convertible-Review.290638.0.html#h_pricecompare_288514_0125283001524971239

Thank you for voting.

Edit: My benchmark list. Not much has been added to it. Might make a new thread and update the list now that I have a whole new spec block that I’m dealing with.

My Stupid List Of Benchmarks, and no not fucking firestrike

I hate synthetic benchmarks so I started inventing my own ridiculous and useful benchmarks. So in the past I have posted about hardware that I have gotten. This is mostly just to show what projects I might do or to pose questions on the thread later on if I am really not getting something. Some of those threads have very weird benchmarks posted with them. These all to test different aspects of what the machine is supposed to do and are rated to different machines. Hi-Calibur machines get one kind, low-calibur another, and mid-range kind of get both but also have their own. At that some are designed to show what I will be doing with the machine and how fast I can expect to be able to do that from boot, closing an app, opening another app, or after setting idle for a minimum of 30 minutes (while the machine gets hot). We’ll start from low to high and go through what they do. The AAAAAAAAAAAA Test: The A test is applicable to any OS with an office suite. This is generally set with linux as I use that the most, but after startup and basic system checks, I generally open an office suite (or install libreoffice) and just hold down A. Could be any key, but A is just there. I keep a stop watch open on my phone and the CPU graph in the task manager. If the machine spikes to 100 I count the seconds between the spikes and count how many times it lags the entrance of text to the document. If it is a high lag time and the CPU graph constantly spikes, I generally go back to an older OS or trime the DE down to the basic essentials. In some cases trimming helps, like a lot. Example: IBM 600X with a Pentium 3 MMX @ 650 MHZ, 386 MB ram, 1997 IDE Bus. The average time for startup on a 7200 RPM drive was around 56 seconds (Xubuntu). Opening the Office Suite (libre office) took 25-27 seconds and while it loaded I held the A key. As soon as the AAAAA started I got 4 in, CPU spiked, then 17, spike, 15, spike, and after another 3 spikes (around 35-45 seconds) it smoo…