3 ms·
The price comparisons are odd/wrong, because it appears he simply calculated the AWS price for a year of that machine. But on the one hand he didn’t need to run
by jtbayly 5y ago
The price comparisons are odd/wrong, because it appears he simply calculated the AWS price for a year of that machine. But on the one hand he didn’t need to run the AWS machine for a year. And on the other hand, he owns the Mac’s for life, as he pointed out. If you wanted to calculate the cost of having the AWS machine always available to you like the Mac, you’d probably at least want to use three years, which is a fairly normal timeframe for a business to write down the cost of a machine.
- RussianCow 5y agoGiven that the use cases for a Mac and an EC2 instance are very different, I don’t think there is a “right” way to compare them.
- ceeplusplus 5y agoThe benchmark itself has some issues; namely, the unit tests are run on a single thread but the end to end tests are merely parallelized one per thread. I would guarantee he's not getting 100% CPU utilization on the M1 machine if those tests are anything like the ones I see. BDD/E2E tests have a lot of waiting for buttons to load on pages, clicking/moving the cursor, and waiting for backend results. A proper test would simply run _all_ the BDD tests in parallel to properly max out the CPU and let the OS handle the thread switching.