Hi Daniel. If you want to to load balance the load on proxy server across multiple machines then you have to use load balancer, Pound is the one we have tested with, it will load balance across all the backend proxies. This is the only way for load balancing on proxy. If you don't want proxy and other storage (object/container/account) working on the same node/machine, as you mentioned in the latest code there is provision to setup remote object/container/account server. Let me know if you are facing any issue with this. If your testing with HTTPS workload then CPU usage will be high due to SSL processing, we observer very low CPU usage with HTTP. Regards, Gaurav ________________________________ From: gluster-users-bounces at gluster.org [gluster-users-bounces at gluster.org] on behalf of Mohammed Junaid [junaid at gluster.com] Sent: Friday, October 28, 2011 12:12 PM To: Daniel Pereira Cc: gluster-users at gluster.org Subject: Re: Gluster object-storage additional proxy Hi Daniel, Please find the comments inline. Yes, I did that. However the CPU usage gets very high (100% for all cores) to have all the Gluster and Swift daemons running on the same machine. We want to separate the processes in the same manner it is already possible in Swift.
