Compressed object filesize VS. OUTPUT Size in the System Load log

[kit]

Hi,

Just curious why the filesize of the compressed object is different from the one shown(OUTPUT SIZE) in the System Load log. Can you please help me understand why? or I guess the question would be "Are they supposed to be the same?". Is the OUTPUT SIZE in using Bytes or Kilobytes? Please see attached file for screenshot.

Thanks,

Kit

[Justin Derrick]

This is likely a rounding error -- 4402 Bytes is bigger than "4K", which is 4096 bytes, which would probably be rounded up to 5K.

It could also be a little bit of overhead associated with the compression method.

I'm sure if you load larger files (in the MB to GB range) you'll see that the discrepancy is practically zero.

-JD.

[Alessandro Perucchi]

There is also something that is hidden behind that number... of course the compression gives a little bit of overhead... but the fact that this size seems off, is because when you use ARSLOAD, it will also store the compressed index entries.

So it means that the number you see is in fact the stored size from compressed Index + all segment part of your document (compressed or not).

And the size is always in bytes.

Hope that answers a little bit your question.