| Thread Previous • Date Previous • Date Next • Thread Next |
On Oct 11, 2012, at 4:28 PM, Alejandro Comisario <alejandro.comisario@xxxxxxxxxxxxxxxx> wrote:Hi Stackers ! This is the thing, today we have a 24 datanodes (3 copies, 90TB usables) each datanode has 2 intel hexacores CPU with HT and 96GB of RAM, and 6 Proxies with the same hardware configuration, using swift 1.4.8 with keystone. Regarding the networking, each proxy / datanodes has a dual 1Gb nic, bonded in LACP mode 4,
Are you seeing good balancing of traffic across the two interfaces in the bonds?
each of the proxies are behind an F5 BigIP Load Balancer ( so, no worries over there ).
What is the "pipe" into/out-of the F5 (cluster of F5's?) and how utilized is that pipe already? If it is running at anything more than 2.5% (5000/200000) to 5.5% (5000/90000) in the direction the GETS will flow it will become a bottleneck. (handwaving it as 100% GETS rather than 90%)
rick jones
Today, we are receiving 5000 RPM ( Requests per Minute ) with 660 RPM per Proxies, i know its low, but now ... with a new product migration, soon ( really soon ) we are expecting to receive about a total of 90.000 RPM average ( 1500 req / s ) with weekly peaks of 200.000 RPM ( 3500 req / s ) to the swift api, witch will be 90% public gets ( no keystone auth ) and 10% authorized PUTS (keystone in the middle, worth to know that we have a 10 keystone vms pool, connected to a 5 nodes galera mysql cluster, so no worries there either ) So, 3500 req/s divided by 6 proxy nodes doesnt sounds too much, but well, its a number that we cant ignore. What do you think about this numbers? does this 6 proxies sounds good, or we should double or triple the proxies ? Does anyone has this size of requests and can share their configs ?
| Thread Previous • Date Previous • Date Next • Thread Next |
