stream: read-cache two blocks?
@egmontkob
Submitted by Egmont Koblinger Link to original bug (#757499)
Description
Currently vtestream caches the last read block (in its decrypted/uncompressed form).
That means that if you slowly scroll while the displayed content (in any of the 3 streams) is at the boundary of two blocks, it continuously reads from disk (well, the kernel's cache), decrypts and deflates.
Would it be better to cache the 2 last used blocks per stream? It'd take up an additional 192 kB per vte, but would save some CPU time. Or is this CPU time negligible to the cost of drawing the characters?
Version: git master