Compression in ParaView Geometry Delivery Edit
The following figure shows delivery time measured in seconds vs. geometry size measured in bytes. Red dots represent no compression while blue dots represent Zlib compression. In clockwise from upper left results obtained over 3 connections are shown, 1) localhost, 2) 100 MB/s, 3) Broadband. The test data was generated using the Sphere Source and increasing the theta and phi resolution by powers of two. A ParaView state file was used to save the test data and can be used to reproduce the results. Note: the plot is log-log so it's not that easy to read, but see the figure where we plot speed up below.
The following figure shows the speed up (left) and compression ratio (right) obtained with the Zlib geometry compressor plotted against the geometry size. The speed over three connects are shown, 1) localhost (cyan), 2) 100 MB/s (yellow) and 3) broadband (green).
The input for the above test were a series of spheres each with a theta and phi resolution increasing by powers of two.
Compression of VTK Datasets Edit
The following tables details the affects of compression on a VTK binary legacy dataset, and the runtime of a compress-decompress cycle. Three compression schemes were compared, bzip2, zlib, and szip. Three similar datasets were used for the comparison. Each was generated by an iso-surface filter applied to some simulation data. The difference between the resulting dataset is their size.
|Input Dataset||Case Number||Scheme Name||Final size||Compression Ratio||Relative Compression Ratio||Time Delta||Relative Time Delta|
The input data were isosurfaces of a test dataset at three levels. The 0.5 level produced the smallest isosurface while the value 0.8 produced a very large isosurface.