News for hackers. Stuff that matters.
Re:The Effects of CPU Turbo: 768X Stddev by shakna on Tuesday July 10, 2018 @03:53AM (#17496129)
If 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.

Re:The Effects of CPU Turbo: 768X Stddev by vanderZwan on Tuesday July 10, 2018 @09:40AM (#17497949)
> 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?

Re:The Effects of CPU Turbo: 768X Stddev by mkhalil on Tuesday July 10, 2018 @11:47AM (#17499116)
I 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.
Re:The Effects of CPU Turbo: 768X Stddev by shakna on Wednesday July 11, 2018 @02:43AM (#17504912)
> 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.