It's written in Ruby and uses the Sinatra streaming API (an EventMachine implementation of Server-sent Events ) to handle both the incoming log data and outgoing live updates to the user's browser.
It uses the Heroku API when you connect to the page to fetch the app's name and number of web dynos . It takes a hint for concurrency per dyno based on the WEB CONCURRENCY config var.
All of the metrics are derived from 60 seconds …
- OnRails.org: Moving onrails.org to Typo 5.4.x, Rails 2.3.8 on Heroku
- LoGeek's software blog: Notes from Sinatra, Heroku and MongoHQ deployment
- Ruby Inside: The Heroku & IndexTank "Build A Search-Based Webapp" Holiday Challenge
- paperplanes: Web Operations 101 For Developers
- RubyLearning Blog: Getting started with Heroku
- Jake Scruggs: Rails Conf 2010 Day 2
The final option for consideration is em-resque - an EventMachine based worker system. There is a great blog post explaining the problems and reasons behind this gem's creation - we're just about to give it a go, so hopefully it will be as good as it looks.
So far, a standard Resque worker in our case can process 120 jobs per minute, the resque-jobs-per-fork set at 500 jobs per fork can manage about 300 jobs per minute (average) while running with no forking (using …
- RubyFlow - Search for jruby: On JRuby, Resque and Windows
- Mike Perham: Background Processing vs Message Queueing
- ones zeros majors and minors: man what
- Ruby News: Red Dirt RubyConf 2010
- Odes of the Occult: Resque Mailer says: Put your emails to background
- paulsturgess.co.uk articles: How to retry a specific queue of failed Resque jobs
…years working to advance and improve Ruby's efficiency through concurrency, first with EventMachine and fibers and now with Actors and multithreading so it shouldn't surprise you that my #1 pick is puma . It's my belief that puma and sidekiq are a new breed of Ruby infrastructure that can dramatically improve your application's efficiency — should you decide to take advantage of them.
puma is a pure Ruby, Rack-based web server and drops right …
- A Fresh Cup: Double Shot #849
- RubyFlow - Search for jruby: JRuby 1.7 Released
- Riding Rails - home: [ANN] Rails 3.1.4 has been released!
- RailsCasts: #376 JRuby Basics
- Ruby Inside: This Week in Ruby: Rails 4 Sneak Peeks, A Gist Drama, and a CoffeeScript Book (by a Rubyist!)
- Headius: An experiment in static compilation of Ruby: FASTRUBY!
And a happy Thanksgiving to you as well.
Colour Schemes - A whole pile of 'em for Sublime Text 2 or TextMate.
Zuck - Gem to use Facebook's ads API.
Cramp - Asynchronous Ruby web application framework built on top of EventMachine.
Skitch and Evernote: A Letter from Keith Lang - Looks like they're actually listening to user feedback. Amazing.
- Giles Bowkett: With Apologies, Some Senseless Ruby Bickering
- Labnotes: Rounded Corners 275 — My name is ...
- Scout ~ The Blog: The nuts and bolts of our Ruby-based realtime charts solution
Goliath does not seem to have official support for JRuby thanks to the unknown status of EventMachine's Java support.
So the only options left were J2EE app servers such as JBoss, Tomcat, GlassFish and TorqueBox; as well as the recently developed Puma, which is almost pure Ruby.
Thanks to the new ApplicationPool and Spawner architecture in Phusion Passenger 4, we're now able to support JRuby with ease. Because a lot of code has been moved into C++, we no longer …
- Phusion Corporate Blog: Phusion Passenger 4.0 beta 2: Syscall failure simulation framework, focus on stability
- Phusion Corporate Blog: Phusion Passenger 4 Technology Preview: Out-Of-Band Work
- elc technologies - Blog : Ruby on Rails, iPhone, Flash, Agile, Interactive Design: JRubyConf 2010
- Engine Yard Developer Blog: Steppin' Out: June Events
- Testing 1,2,3...: Why not use FFI? Here's why.
- Odes of the Occult: Open3 And The PID Of The Spawn
Describing a slide deck with ' Ruby developers need to stop using EventMachine. It's the wrong direction' is a sure-fire way to get attention :-)
Growing a Rails Application: How We Made Deploy Fast Again
The developers at PagerDuty brought their deploy time down from 10 minutes to 50 seconds. How? You gotta read for that.
Watching and Listening
Aaron Patterson on ' Rails 4 and the Future of Web'
Earlier this month at Aloha Ruby Conference 2012…
- Zach Inglis: Calling all designers!
- New Relic: Get Ready to Rumble: Join Us This Weekend at Rails Rumble 2012
- Coding Horror: Judging Websites
- A Fresh Cup: Double Shot #958
- Rails Rumble: Just When You Thought You Were Out...
- casperfabricius.com: Learnings from Rails Rumble
Ruby's EventMachine: Event-based Programming (Part 1)
Not up to speed with EventMachine yet? No worries, Phil Whelan kicks off a series of blog posts introducing us to the popular event-processing library (which, incidentally, hit version 1.0 just this month.)
An Experiment in Static Compilation of Ruby: FastRuby
Charles Nutter (of JRuby fame) shows off an experiment in doing static compilation of Ruby to Java. Short and sweet and leans on JRuby…
- New Relic: I Don't Always Monitor My Rails Apps, But When I Do I Use New Relic
- A Fresh Cup: Double Shot #914
- Plataformatec Blog: Eager loading for greater good
- Invisible Blocks: Out of Love with Active Record
- Signal vs. Noise: 37signals invests in The Starter League
- Viget.com Blogs: A Better Way to Add a ‘selected' Class to Links in Rails
…was the only application server that was able to support high I/O concurrency use cases. Built on EventMachine, Thin is evented, just like Node.js. Since then, another evented application server called Goliath has appeared, also built on EventMachine. However, evented servers require evented application code, and Rails is clearly not evented.
There have been attempts to make serial-looking code evented through the use of Ruby 1.9 fibers, e.g. through the em-synchrony gem , …
- A Fresh Cup: Double Shot #930
- Phusion Corporate Blog: Phusion Passenger 4.0 beta 1 is here
- WyeWorks Blog - The Team's Voice: Rails 4 compilation links
- Phusion Corporate Blog: The new Rack socket hijacking API
- Labnotes: Rounded Corners 333 - Amazeballs
- A Fresh Cup: Double Shot #797
Note : If you end up enjoying this post, you should do two things (I am paying customers for both and get nothing in return). sign up for Pusher and then subscribe to destroy all software screencasts , or vice versa.
For those that do not know, Gauges currently uses Pusher.com for flinging around all the traffic live.
Every track request to Gauges sends a request to Pusher. We do this using EventMachine in a thread, as I have previously written about .
- RailsTips by John Nunemaker: More Tiny Classes
- Redline Software Inc. - Winnipeg's Leader in Ruby on Rails Development: Intro to BDD presentation
- A Fresh Cup: Double Shot #797
- Giles Bowkett: I'm Totally Against Killing Hollywood
…and weaknesses, though the most common is EventMachine. Just like our simple reactor, EventMachine offers timers and asynchronous handling of events, though EventMachine's versions will scale better. This article's version uses the select() call, which limits code using it to 1024 open file descriptors. On the other hand, EventMachine, if used on a platform that support epoll ( Linux) or kqueue (various * BSD platforms), can readily support at least 10s of thousands. EventMachine…
- PeepCode Products: Meet EventMachine: Part I
- kahfei: thin on windows
- Running & Coding: Juggernaut, Push Server, The future of the web
- igvita.com: Untangling Evented Code with Ruby Fibers
- Jonathan Conway: Starting from scratch
- oldmoe: Building the Never Blocking Rails, Making Rails 12X Faster