> [...] Not sure if this can be solved with reducing S3QL block size... I do not think so – you would need to reduce the max block size to 128KiB – do not do that!
Your best option probably will be to use a huge S3QL cache (on SSD) and try to keep that cache as long as you can (option "--keep-cache" see https://www.rath.org/s3ql-docs/mount.html#mounting) Eventually your metadata will be all cached and you will have near local performance. -- 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 s3ql+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/be699ee6-71fe-5e60-85e0-872745ac7679%40jagszent.de.
