of the GlusterFS servers and then increased the Proxy server count. If there are any other GlusterFS servers then you can start Gluster Object Storage on those machines and do some load balancing over all these machines by using Pound, nginx etc. This will help reduce the cpu usage of the current machine and also utilize the other server resources. I read the documentation and there's no mention about separating the > swift/object-storage servers in such way. I already have a working setup, I > just need to add more proxies. > I could, of course, setup two sets of independent servers and somehow do a > messy data sharding between the two servers, but it's simpler and cheaper to > scale just the proxy servers as needed (this is almost standard procedure in > Swift) since, from our measurements, they are the bottleneck. > There is a difference here how the swift and Gluster Object Storage work. Currently, all the servers (proxy, auth, object, etc) are all coupled to each other and hence they cannot be seperated. This can be emulated by configuring the setup as I mentioned above. Hope this helps. Thanks, Junaid --f46d04451a83bfb51604b0563131 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Daniel,<br><br><div>Please find the comments inline.</div><div><br></div= ><div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D= "margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Yes, I did= that. However the CPU usage gets very high (100% for all cores) to have al= l the Gluster and Swift daemons running on the same machine. We want to sep= arate the processes in the same manner it is already possible in Swift.</bl= ockquote> <div><br></div><div>From what I understand, you have started the Gluster Ob= ject Storage on one of the GlusterFS servers and then increased the Proxy s= erver count. If there are any other GlusterFS servers then you can start Gl= uster Object Storage on those machines and do some load balancing over all = these machines by using Pound, nginx etc. This will help reduce the cpu usa= ge of the current machine and also utilize the other server resources.</div= > <div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex= ;border-left:1px #ccc solid;padding-left:1ex;"> I read the documentation and there's no mention about separating the sw= ift/object-storage servers in such way. I already have a working setup, I j= ust need to add more proxies.<br> I could, of course, setup two sets of independent servers and somehow do a = messy data sharding between the two servers, but it's simpler and cheap= er to scale just the proxy servers as needed (this is almost standard proce= dure in Swift) since, from our measurements, they are the bottleneck.<br> </blockquote><div><br></div><div>There is a difference here how the swift a= nd Gluster Object Storage work. Currently, all the servers (proxy, auth, ob= ject, etc) are all coupled to each other and hence they cannot be seperated= . This can be emulated by configuring the setup as I mentioned above.</div> <div><br></div><div>Hope this helps.</div><div><br></div><div>Thanks,</div>= <div>Junaid</div></div></div> --f46d04451a83bfb51604b0563131--
