Compressed writer can write too much, if flush() called when nothing to write

Examining the stats for serial4a.ecl (regression test program), showed a spillwrite activity recording a "SizeDiskWrite" as 308 (across 4 nodes=284+8+8+8).  The related spillread showed that 1048832 bytes were read. .

The spilled were compressed files which had a 1MB cache/block size.  This explains the large spill read size. 

I believe the 308 bytes is the actual size written of the data for the spill file and 1048832 may be the physical size written to disk, cause from the use of compressed file type & 1MB block size.

However, this it is still confusing to observe that a large read was made from what appears to be a small file.

jakesmith ghalliday