Here is what super-compression looks like two weeks before release:
A test project that generates 10 million random values, then converts them to text, saves into a file, and re-reads it.
Version 4.2.1 (current release), no super-compression, run time 59 s, RAM 4.3GB.
Version 4.2.2 (beta), super-compression is on, run time 37 s, RAM 1.4GB.
Remarks and observations:
- The bigger datasets, the better the gains from super-compression
- In projects with relatively small datasets and lots of actions the super-compression has a moderate effect
- Super-compression is generally stable but we want to keep it in experimental mode for couple releases, just in case. In v4.2.2 it will be turned ON by default in Launcher, and by default OFF in Desktop and Server.
- Super-compression has basically no performance overhead. In I/O heavy workflows (as in the test above) it even improves performance.
- We’re intended to make super-compression always on after a couple releases. However, the final decision will be made after examining field reports.