On 2020-07-10 at 15:41 +0200, Daniel Jagszent wrote: > > [...] 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!
Indeed, I understand it won't fly. > > 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. As I see it, borg apparently does not keep its metadata tightly grouped -- metadata chunks may end up in completely random segments. I have 100 GiB allocated for s3ql cache and it does not appear to help much. -- Ivan Shapovalov / intelfx / -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/ebb1733584f219ff005b2a92230803ecac5c0584.camel%40intelfx.name.
signature.asc
Description: This is a digitally signed message part
