7 ms·
So.. the author is focusing on metrics - the memory usage. Basicly what's being done is release the caching sooner. Well what if a user's usecase scenario is su
by hbogert 12y ago
So.. the author is focusing on metrics - the memory usage. Basicly what's being done is release the caching sooner. Well what if a user's usecase scenario is such that he's looking at 2 pages after another a few times which have 10 pages in between.. This would cause a lot more rerenderings than before, making CPU go up. I'm not sure if I want to trade memory for CPU when running on battery
- nnethercote 12y agoSoftware is full of trade-offs. If slightly pessimizing an unusual case is the cost of drastically improving an extremely common case, then I'm happy to do that.
- pessimizer 12y agoSwitching between two non-consecutive pages in a pdf is not an unusual case.
- nnethercote 12y agoSwitching by scrolling, or by jumping directly to the pages using a page selector? The latter case will be handled fine by a 10 page cache. Anyway, I think this fear is overblown. The CPU cost of rendering a single page isn't that high.