7 ms·
The Effects of CPU Turbo: 768X Stddev
- praseodym 8y agoDuplicate of https://news.ycombinator.com/item?id=17485536 https://news.ycombinator.com/item?id=17485536
- ddorian43 8y agoThat one is empty,old and with no upvotes.
- regularfry 8y agoThat page seems to make Android Chrome hang.
- Pieman103021 8y agoNo issues like that here. On a Huawei Honor 7x with Android 8.0.0
- shakna 8y agoIf that's happening to you, then it's probably an issue with asciinema and your particular version of Android's Chrome. That's most of the JS on the page. That being said, the page transfers ~500Kb, and loads into memory ~30Mb, which shouldn't be that substantial. Most of it lies in the asciinema player (which should be mostly JITing), or an array.
- vanderZwan 8y ago> loads into memory ~30Mb Is that the asciinema player, or the "video" it plays? Either way: I thought part of the point of asciinema was that it compresses better for terminal capture? Just how much data was stored by that particular session?
- mkhalil 8y agoI think it compresses file size/network transfer, but in order for playback to occur, the video must be decompressed into memory, even though the terminal colors will be mostly the same color hex.
- shakna 8y ago> Is that the asciinema player, or the "video" it plays? Hard to tell, just shows up as 'JIT' in the profiler. > I thought part of the point of asciinema was that it compresses better for terminal capture? Better than what? 30Mb of heap for a video source/player combination isn't that awful. It's on-par with most videos that your web browser will try to play.
- tomalpha 8y agoEnsure that your BIOS says performance when connected to AC This was the most interesting tidbit for me. It wouldn’t occur to me to run benchmarks on a laptop (I guess due to my advancing years...)
- agallego 8y agoThanks. That machine has a server processor and ecc memory 64GB. Specs are pretty similar to a small server. But yeah. Hardware has changed a ton :)
- richardwhiuk 8y agoWith credit to the author, it feels like they found out something interesting, but the article feels like a mess. On one hand, they made a performance optimisation to a library - cool. On the other hand, the title and the conclusion talk about the difference between turbo boost in a CPU, which seems completely missing from the articles contents....
- SiempreViernes 8y agoThere is a bit of connecting transitions missing, but basically I understand it thus: He was using a slower buffer serialisation library (for reasons unexplained), and when challenged set out to prove his choice was the fastest, but pretty soon found out he was wrong. Then he wanted to do the test himself, and along the way he discovered how his processor made benchmarking very noisy in turbo mode.
- agallego 8y agoThanks for summarizing it better than I did. I'll edit and make that a bit more clear.
- ianhowson 8y agoPlenty of other data points in the table show reduced stddev with turbo enabled. The 768x line looks like an anomaly. Without knowing how many runs were made and the other test conditions, it's difficult to know what actually changed. There's far too much noise in the table to come to the conclusion that turbo was the culprit. We're only talking about a 30% difference in clock rate for 3.2GHz vs 4.2GHz. If there's more change than that across turbo vs. non-turbo, something else in the benchmark setup is messed up.
- agallego 8y ago~20%. The difference however is a max of ~2.3x in that direction. 100% of the code is there, what do you suggest is 'messed' up. I probably ran the benchmarks 100s of times over 7 days trying to understand. That particular I posted seemed aligned with the others, but that was the stddev of 3 runs provided by Google Benchmark --benchmark_repetitions=3 I made it 10 and not much difference there. That was the point of 768X anomalies. The values are never like that w/ capped frequencies.
- ianhowson 8y agoHang on, so we've got: - SD increase of 768x - Mean increase of 1.2 to 2.3x - But n=3? You need a lot more samples to make a reasonable statement about whether Turbo had an impact or not. Noise is completely overpowering your measurements. AFAICT, you're measuring SD of the time (nanoseconds) to run your task, and mean is around 9000ns. 1ns SD is abnormally low, and 768ns SD seems about right (this is a desktop machine, after all). But I couldn't really figure this out from the article.
- agallego 8y agoNo no. - capped freqs: stddev 768x. in the non-turbo-to-turbo direction - in the other direction it is 2.3x. So was just acknowledging that there are 20% of samples in that table with your previous point
- 8y ago
- dagenix 8y agoMinor: ”Friday, June 28 2018". June 28th was actually a Thursday this year.
- agallego 8y ago... i guess I was tired when i wrote it. I meant to write 29th! thanks!!