Show HN: goworker – a faster, Resque-compatible background worker
> <i>For simple dequeuing, deserialization, execution, and updating stats (as with the Hello worker above), goworker is 80x faster than Resque and 23x faster than Sidekiq.</i><p>In real world use cases, how often is that kind of overhead a significant portion of total run time, compared with the actual work?  If it's a small portion, would that make the speed up fairly irrelevant, does it actually speed up real world use cases significantly?<p>Of course, your actual work payload may be faster too in go than ruby if you know how to write it well.