Here are two consecutive readings from s3qlstat on an Amazon S3 store
that is being written to:
Directory entries: 6011
Inodes: 6015
Data blocks: 351716
Total data size: 3.40 TB
After de-duplication: 3.33 TB (97.83% of total)
After compression: 3.33 TB (97.73% of total, 99.90% of de-duplicated)
Database size: 49.6 MiB (uncompressed)
Cache usage: 39.1 GiB (dirty: 8.58 MiB)
Directory entries: 6012
Inodes: 6016
Data blocks: 351778
Total data size: 3.40 TB
After de-duplication: 3.33 TB (97.83% of total)
After compression: 3.33 TB (97.73% of total, 99.90% of de-duplicated)
Database size: 49.6 MiB (uncompressed)
Cache usage: 39.1 GiB (dirty: 11.9 MiB)
My question is this: It seems clear that at least 3.1 MiB has been
written so why has the cache usage not gone up? mount.s3ql was called
with:
--allow-other --fg --metadata-upload-interval 3600 --compress none
--cachesize 524288000
and mount.log reports:
s3ql.mount.main: Setting cache size to 1404564 MB
Also why is it saying a 1.3 TB cache size when I requested 500 GB?
Regards
Cliff.
--
Cliff Stanford
Office: +44 20 0222 1666 UK Mobile: +44 7973 616 666
Spain: +34 952 587 666
http://www.may.be/
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
