On 03/05/2016 03:45 PM, Oleksandr Natalenko wrote:
In order to estimate GlusterFS arbiter brick size, I've deployed test setup
with replica 3 arbiter 1 volume within one node. Each brick is located on
separate HDD (XFS with inode size == 512). Using GlusterFS v3.7.6 + memleak
patches. Volume opti
Hi.
On вівторок, 8 березня 2016 р. 19:13:05 EET Ravishankar N wrote:
> I think the first one is right because you still haven't used up all the
> inodes.(2036637 used vs. the max. permissible 3139091). But again this
> is an approximation because not all files would be 899 bytes. For
> example if
On 03/16/2016 10:57 PM, Oleksandr Natalenko wrote:
OK, I've repeated the test with the following hierarchy:
* 10 top-level folders with 10 second-level folders each;
* 10 000 files in each second-level folder.
So, this composes 10×10×1=1M files and 100 folders
Initial brick used space: 33
Ravi,
here is the summary: [1]
Regards,
Oleksandr.
[1] https://gist.github.com/e8265ca07f7b19f30bb3
On четвер, 17 березня 2016 р. 09:58:14 EET Ravishankar N wrote:
> On 03/16/2016 10:57 PM, Oleksandr Natalenko wrote:
> > OK, I've repeated the test with the following hierarchy:
> >
> > * 10 t
OK, I've repeated the test with the following hierarchy:
* 10 top-level folders with 10 second-level folders each;
* 10 000 files in each second-level folder.
So, this composes 10×10×1=1M files and 100 folders
Initial brick used space: 33 M
Initial inodes count: 24
After test:
* each brick
Thanks Oleksandr! I'll update
http://gluster.readthedocs.org/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/
with a link to your gist.
On 03/18/2016 04:24 AM, Oleksandr Natalenko wrote:
Ravi,
here is the summary: [1]
Regards,
Oleksandr.
[1] https://gist.github.com/e8265ca07f7
Ravi, I will definitely arrange the results into some short handy
document and post it here.
Also, @JoeJulian on IRC suggested me to perform this test on XFS bricks
with inode size of 256b and 1k:
===
22:38 <@JoeJulian> post-factum: Just wondering what 256 byte inodes
might look like for tha
And for 256b inode:
(597904 - 33000) / (1066036 - 23) == 530 bytes per inode.
So I still consider 1k to be good estimation for average workload.
Regards,
Oleksandr.
On четвер, 17 березня 2016 р. 09:58:14 EET Ravishankar N wrote:
> Looks okay to me Oleksandr. You might want to make a github gi
