Blog
Blog
Rails Middleware Timing with Rack Timer
- 03/14/2012, 8:45am (CDT)
Better Living with Enumerated Field
- 09/20/2011, 9:22am (CDT)
TST Media: The Evolution of Entrepreneurship
- 09/02/2011, 7:14am (CDT)
Torspo: Tradition, Reinvented
- 07/25/2011, 1:17pm (CDT)
Deploying when Removing Columns with Rails with Zero Downtime
- 07/11/2011, 8:00am (CDT)
The 2011 TST Media Ping Pong Classic: A Retrospective in Sporting Excellence
- 07/08/2011, 8:14am (CDT)
Ready to get your blog on?
- 06/14/2011, 1:19pm (CDT)
"We've Landed on the Moon!"
- 06/02/2011, 8:39am (CDT)
Minnesota Lacrosse and TST Media: Anatomy of a sport's boom
- 05/27/2011, 12:04pm (CDT)
TST Media: The Entrepreneurial Spirit is Alive and Well
- 05/18/2011, 2:43pm (CDT)
Rails 3 Performance - Not Good Enough
- 05/11/2011, 8:53am (CDT)
TST Media Jumps Across the Pond
- 04/27/2011, 2:13pm (CDT)
5 easy tips to improve your website’s user experience
- 04/20/2011, 12:36pm (CDT)
NGIN Receives An Overhaul - Upgraded To Rails 3
- 04/15/2011, 2:00pm (CDT)
Social Media Do’s and Don’ts
- 04/11/2011, 1:51pm (CDT)
View All |
Recent Comments
We later determined that the remaining 100ms of request queuing was entirely due to SSL. By taking one key request off of SSL that did not need to be on SSL we were able to cut our "request queuing" time down to an average of 40 ms per request. Non SSL requests experience a 1-5 ms of request queuing time, while SSL requests are closer to 500 ms.
Rack Timer has been tested with Rails 3.0.10 and at a glance I can tell it is NOT compatible with Rails 3.1.x. The MiddlewareStack class which is overridden by Rack Timer has changed from inheriting from Array in 3.0.x to having an Array in 3.1.x branch.
Looks pretty good. I'm wondering though, why reinvent enumerated_attribute? https://github.com/jeffp/enumerated_attribute
What are the pros and cons of each?