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

Puma middleware #1

Merged
merged 2 commits into from
Jan 30, 2014
Merged

Puma middleware #1

merged 2 commits into from
Jan 30, 2014

Conversation

krasnoukhov
Copy link
Contributor

Equivalent middleware for Puma server.

@tmm1
Copy link
Owner

tmm1 commented Jan 30, 2014

Nice. I didn't know about this after reply trick. Is it only implemented in Puma?

tmm1 added a commit that referenced this pull request Jan 30, 2014
@tmm1 tmm1 merged commit 01b3863 into tmm1:master Jan 30, 2014
@krasnoukhov
Copy link
Contributor Author

Yes, looks like it's Puma-only thing.
I've found it here: rack/rack#587

@chetan
Copy link

chetan commented Jan 30, 2014

I'm not sure this makes sense in a threaded environment. Wouldn't the OOBGC be triggered concurrently (and needlessly) under load? Even on a lightly loaded system, the OOBGC will run while other requests are being processed which defeats the purpose.

@tmm1
Copy link
Owner

tmm1 commented Jan 30, 2014

Good point. The way oobgc works is by measuring the number of allocations between calls to run, so invoking it on multiple threads will throw off the self-tuning as well.

@krasnoukhov
Copy link
Contributor Author

Ok, this is what I was afraid of. Is there any workarounds or different schemes that can be applied?

tmm1 added a commit that referenced this pull request Jan 30, 2014
tmm1 added a commit that referenced this pull request Jan 30, 2014
@tmm1
Copy link
Owner

tmm1 commented Jan 30, 2014

Reverted for now. I'm not sure how OOBGC should work in this scenario.

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