Interested as well by what kind of workload clients are sending.
Sorry I did not read that comment until the very end :) Did you notice less performance with less clients? ie. does it plateau after a 20 clients?
In your case if you upload files one by one, you'll always be limited by the IO on one node. Are you uploading multiple files in parallel? What does the iowait looks like on the nodes?
Depending on what the underlying hardware is, you would likely get better perf (but lower available storage) by ditching RAID6 and leveraging [multi-hdd](https://garagehq.deuxfleurs.fr/documentatio…
Can you detail how you access the nodes? Is there a load balancer in front? Are you hitting a single node? What's the replication and the layout like?
Quickwit is a log storage and query backend, so it can be abused (with tricot HTTP logs) to get statistics on website request from a backend PoV, but it's definitely not in itself a tracking tool…
Do we really need something as low as 60s ? Would 300s do?
@lx would directing all create bucket calls to a single node alleviate somewhat that effect?
As a storage backend, what prevents you from hosting garage on the NAS itself or though something like iSCSI?
Fundamentally it should be possible, as garage doesn't really do anything fancy with the underlying file system. At least for the data folder. For the metadata, things could be more tricky…
Just came back from travel. Your last set of screenshots confirm what the resync queue is showing: those nodes don't seem to be able to get those blocks anywhere, or they have a corrupted…