For anyone else who didn't know:<p>> Run-length encoding (RLE) is a very simple form of lossless data compression in which runs of data (that is, sequences in which the same data value occurs in many consecutive data elements) are stored as a single data value and count, rather than as the original run. This is most useful on data that contains many such runs. Consider, for example, simple graphic images such as icons, line drawings, and animations. It is not useful with files that don't have many runs as it could greatly increase the file size.<p>> RLE may also be used to refer to an early graphics file format supported by CompuServe for compressing black and white images, but was widely supplanted by their later Graphics Interchange Format. RLE also refers to a little-used image format in Windows 3.x, with the extension rle, which is a Run Length Encoded Bitmap, used to compress the Windows 3.x startup screen.<p>> Typical applications of this encoding are when the source information comprises long substrings of the same character or binary digit.<p><a href="https://en.wikipedia.org/wiki/Run-length_encoding" rel="nofollow">https://en.wikipedia.org/wiki/Run-length_encoding</a>
Hi powturbo! Seeing as these benchmarks are for Sandy Bridge, I thought it would be interested to see how the numbers changed for Haswell and Skylake. I couldn't immediately figure out how to replicate the benchmark, though. Could you give (or point to) some explicit directions on the steps to follow? Thanks.