search for: apkmirror_data1

...at which point if we went live, I'm not even sure gluster would be able to keep up instead of bringing the machines and services down. Here's the cluster config, though it didn't seem to make any difference performance-wise before I applied the customizations vs after. Volume Name: apkmirror_data1 Type: Replicate Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e Status: Started Snapshot Count: 0 Number of Bricks: 1 x 4 = 4 Transport-type: tcp Bricks: Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 Brick2: forge:/mnt/forge_block1/apkmirror_data1 Brick3: hive:/mnt/hive_block1/apkmirror_data1 B...

...not even sure > gluster would be able to keep up instead of bringing the machines and > services down. > > > > Here's the cluster config, though it didn't seem to make any difference > performance-wise before I applied the customizations vs after. > > Volume Name: apkmirror_data1 > Type: Replicate > Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 4 = 4 > Transport-type: tcp > Bricks: > Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 > Brick2: forge:/mnt/forge_block1/apkmirror_data1 &g...

Hi, I'm trying to squeeze performance out of gluster on 4 80GB RAM 20-CPU machines where Gluster runs on attached block storage (Linode) in (4 replicate bricks), and so far everything I tried results in sub-optimal performance. There are many files - mostly images, several million - and many operations take minutes, copying multiple files (even if they're small) suddenly freezes up for

...be able to keep up instead of bringing the machines and >> services down. >> >> >> >> Here's the cluster config, though it didn't seem to make any difference >> performance-wise before I applied the customizations vs after. >> >> Volume Name: apkmirror_data1 >> Type: Replicate >> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 4 = 4 >> Transport-type: tcp >> Bricks: >> Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 >> Brick2: forge:...

...ringing the machines >>> and services down. >>> >>> >>> >>> Here's the cluster config, though it didn't seem to make any difference >>> performance-wise before I applied the customizations vs after. >>> >>> Volume Name: apkmirror_data1 >>> Type: Replicate >>> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >>> Status: Started >>> Snapshot Count: 0 >>> Number of Bricks: 1 x 4 = 4 >>> Transport-type: tcp >>> Bricks: >>> Brick1: nexus2:/mnt/nexus2_block1/apkmirr...

...not even sure > gluster would be able to keep up instead of bringing the machines and > services down. > > > > Here's the cluster config, though it didn't seem to make any difference > performance-wise before I applied the customizations vs after. > > Volume Name: apkmirror_data1 > Type: Replicate > Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 4 = 4 > Transport-type: tcp > Bricks: > Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 > Brick2: forge:/mnt/forge_block1/apkmirror_data1 &g...

...;> and services down. >>>> >>>> >>>> >>>> Here's the cluster config, though it didn't seem to make any difference >>>> performance-wise before I applied the customizations vs after. >>>> >>>> Volume Name: apkmirror_data1 >>>> Type: Replicate >>>> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >>>> Status: Started >>>> Snapshot Count: 0 >>>> Number of Bricks: 1 x 4 = 4 >>>> Transport-type: tcp >>>> Bricks: >>>> Brick1: n...

...;>>>> >>>>> >>>>> >>>>> Here's the cluster config, though it didn't seem to make any >>>>> difference performance-wise before I applied the customizations vs after. >>>>> >>>>> Volume Name: apkmirror_data1 >>>>> Type: Replicate >>>>> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >>>>> Status: Started >>>>> Snapshot Count: 0 >>>>> Number of Bricks: 1 x 4 = 4 >>>>> Transport-type: tcp >>>>> Bricks...

...services down. > > > > Here's the cluster config, though it didn't seem > to make any difference performance-wise before I > applied the customizations vs after. > > Volume Name: apkmirror_data1 > Type: Replicate > Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 4 = 4 > Transport-type: tcp &gt...

...t;>>>> >>>>>> >>>>>> Here's the cluster config, though it didn't seem to make any >>>>>> difference performance-wise before I applied the customizations vs after. >>>>>> >>>>>> Volume Name: apkmirror_data1 >>>>>> Type: Replicate >>>>>> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >>>>>> Status: Started >>>>>> Snapshot Count: 0 >>>>>> Number of Bricks: 1 x 4 = 4 >>>>>> Transport-type: tcp &gt...

...gt;>>>>>> >>>>>>> Here's the cluster config, though it didn't seem to make any >>>>>>> difference performance-wise before I applied the customizations vs after. >>>>>>> >>>>>>> Volume Name: apkmirror_data1 >>>>>>> Type: Replicate >>>>>>> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >>>>>>> Status: Started >>>>>>> Snapshot Count: 0 >>>>>>> Number of Bricks: 1 x 4 = 4 >>>>>>>...

...t; >> Here's the cluster config, though it didn't >> seem to make any difference performance-wise >> before I applied the customizations vs after. >> >> Volume Name: apkmirror_data1 >> Type: Replicate >> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 4 = 4 >>...

...gt;>> >>>>>>>> Here's the cluster config, though it didn't seem to make any >>>>>>>> difference performance-wise before I applied the customizations vs after. >>>>>>>> >>>>>>>> Volume Name: apkmirror_data1 >>>>>>>> Type: Replicate >>>>>>>> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >>>>>>>> Status: Started >>>>>>>> Snapshot Count: 0 >>>>>>>> Number of Bricks: 1 x 4 = 4 >>...

...> didn't seem to make any difference >>> performance-wise before I applied >>> the customizations vs after. >>> >>> Volume Name: apkmirror_data1 >>> Type: Replicate >>> Volume ID: >>> 11ecee7e-d4f8-497a-9994-ceb144d6841e >>> Status: Started >>>...