Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add cheaper_busyness plugin to default build profile #229

Merged
merged 1 commit into from
Apr 16, 2013
Merged

add cheaper_busyness plugin to default build profile #229

merged 1 commit into from
Apr 16, 2013

Conversation

prymitive
Copy link
Contributor

I've been using it since first release and it works really well, it would be nice to have it in default build profile.

@anthonyrisinger
Copy link
Contributor

i'd throw an ACK at this, whatever it's worth. we deployed it throughout this last (US) tax season and it handled nonstop variation between full-stop <=> continuous-onslaught rather beautifully... traffic was gobs of SOAP/ReST API (server+client), static content, Django everywhere, and some smaller frameworks/XHR-ness/etc i forget the names of.

...at any rate, this plugin's more "anticipatory" style ("keep more than enough hot to handle the expected-immediate-load" vs. "oh !@#$! please wait [block] while i buckle my pants") better matches the similar expectations/latencies/perf we hold of our production stacks (eg. "hot 'n ready")

unbit added a commit that referenced this pull request Apr 16, 2013
add cheaper_busyness plugin to default build profile
@unbit unbit merged commit d445418 into unbit:master Apr 16, 2013
@unbit
Copy link
Owner

unbit commented Apr 16, 2013

It's ok for me, but please review docs as i do not know if they are updated with latest additions

@prymitive prymitive deleted the cb_in_base branch April 16, 2013 08:14
@prymitive
Copy link
Contributor Author

I need to document 2 backlog related options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants