Closed Bug 1448972 Opened 8 years ago Closed 8 years ago

investigate max concurrent connections limit on ELB

Categories

(Cloud Services Graveyard :: Operations: Autopush, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rpapa, Unassigned)

References

Details

:oremj, I'm in the process of running some comparative loadtests for autopush{-rust}, but hitting the connection limit. do you by chance have any results from your TCP connection test or have you heard back any more from Amazon on this? Also, would you be able to remove the 100K limit that's currently set on autopush STAGE? Thanks!
Flags: needinfo?(oremj)
QA Contact: rpappalardo
-------------------------- SUMMARY -------------------------- CONNECTION TEST a comparative connection test of autopush and autopush-rust endpoints on STAGE, show that we hit a ~65K connection limit for both when connecting through ELB. AUTOPUSH-RUST CONNECTION TEST able to establish approximately 260K connections when we do an ELB bypass (at least with the m4.large). though :benbangert was able to get 3x that many connections w/ a similar test, ultimately we'll be limited by the ELB anyway so, perhaps moot point.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(oremj)
Resolution: --- → FIXED
-------------------------- UPDATE -------------------------- CONNECTION TEST I re-tested both autopush & autopush-rust through the ELB and was able to repeatedly get both up to 112.4K connections. The 65K limit we were reaching before may have been a by-product of running tests on an un-warmed ELB.
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.