Displaying 2 results from an estimated 2 matches for "38001e29".
Did you mean:
380012
2018 Mar 12
0
Expected performance for WORM scenario
Hi,
Can you send us the following details:
1. gluster volume info
2. What client you are using to run this?
Thanks,
Nithya
On 12 March 2018 at 18:16, Andreas Ericsson <andreas.ericsson at findity.com>
wrote:
> Heya fellas.
>
> I've been struggling quite a lot to get glusterfs to perform even
> halfdecently with a write-intensive workload. Testnumbers are from gluster
>
2018 Mar 12
4
Expected performance for WORM scenario
Heya fellas.
I've been struggling quite a lot to get glusterfs to perform even
halfdecently with a write-intensive workload. Testnumbers are from gluster
3.10.7.
We store a bunch of small files in a doubly-tiered sha1 hash fanout
directory structure. The directories themselves aren't overly full. Most of
the data we write to gluster is "write once, read probably never", so 99%