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

Let's extend this a bit... #2

Open
ylluminate opened this issue Jul 21, 2014 · 0 comments
Open

Let's extend this a bit... #2

ylluminate opened this issue Jul 21, 2014 · 0 comments

Comments

@ylluminate
Copy link

So I really appreciated your test here. I understand why you did what you did, but I think it is going to not get proper attention until we extend the test a little to encompass more real world use case scenarios in the way of processing and so forth.

For example, I mentioned this to DHH (https://twitter.com/ylluminate/status/491330900928765952) and he quickly discounted it for this very reason.

I, on the other hand, do see value in what you did and actually have seen essentially the same results independently from an application serving standpoint. Right now we're moving everything to TorqueBox due to seeing these kinds of results. BUT, I really would like for some folks like Rails Core to stand up and say, "Hey, let's do a better job at profiling and really optimizing the crazy heck out of things." or something of that nature. I sincerely believe that more can be done, but it might require some creative thinking and hitherto unexplored options... but we're not going to get there until folks say "Oh, this is more than just Hello World."

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

No branches or pull requests

1 participant