5 ms·
this improvement really isn't going to buy me much I think what they were saying is that they wanted to benchtest raw Passenger performance instead of Rails pe
by sabat 16y ago
this improvement really isn't going to buy me much
I think what they were saying is that they wanted to benchtest raw Passenger performance instead of Rails performance. Your Rails app will almost certainly see some benefit from Passenger 3, but they didn't want to distort their testing by throwing Rails into the mix. Makes sense to me.
- davidw 16y agoThat they wanted to benchmark their own stuff rather than Rails is blatantly obvious. My point is that if, in my Rails app, 5% of the time is taken up by Passenger in a typical request, even big improvements like these are just not going to mean much in the real world. Perhaps they can shed some light on what real world percentages of request time for Passenger vs Rails+App might look like.
- FooBarWidget 16y agoWell the thing is there is no such thing as a single "real world percentage". If you want to know what the percentage is for you, you should benchmark it yourself.
- davidw 16y agoA Hello World page would give a good lower bound for Rails' part of things, I think... Beyond that, it's only going to take up more of the total, right?
- sabat 16y agoThat they wanted to benchmark their own stuff rather than Rails is blatantly obvious. I'm not so sure of that considering your original comment. That's why I explained it to so plainly. The rest is unimportant detail.