757992 - bigtent: load-test staging

Status: RESOLVED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Pete Fritchman [:petef]]

load test on staging; might need to tweak VM RAM, etc.

Comment 1

[Austin King [:ozten]]

We're very early in working on a load testing tool[1], but it is a blocker for code complete (as Pete has recommended sooner than later).

I don't think we want to hit 3rd party servers, but the OpenID or OAuth token verification step would cause outbound requests from BigTent[2].

A rough sketch was to put a proxy between bigtent and 3rd party servers, which we could 'prime' with answers. I was expecting to do this locally (or a dedicated load env), but would this be a good idea on the stage server? If so, how? Can we pragmatically populate a squid or other cache so that a request with a query string returns a pre-determined response?

I was probably going to look at node's 'http-proxy' module, which seems wrong to be pushing onto stage.

Total open to alternative ways to provide data to BT to exercise it's code paths.

[1] https://github.com/mozilla/browserid-bigtent/issues/11
[2] https://github.com/mozilla/browserid-bigtent/issues/23

Comment 2

[Gene Wood [:gene]]

Austin, what are your current thoughts on load testing for bigtent. Are you able to load test currently? If not can I help enable that?

Comment 3

[Austin King [:ozten]]

(In reply to Gene Wood [:gene] from comment #2)

I've updated https://github.com/mozilla/browserid-bigtent/issues/11#issuecomment-11893666 with the current status and what we need to improve the state of load testing.