Skip to content
Commits on Feb 26, 2013
  1. @sferik

    Prep for release 0.4.2

    sferik committed Feb 26, 2013
Commits on Feb 25, 2013
  1. @sferik

    Merge pull request #37 from shiroginne/master

    Wrong UPDATE sql query for postgresql db
    sferik committed Feb 25, 2013
  2. @shiroginne
Commits on Feb 14, 2013
  1. @sferik
Commits on Feb 12, 2013
  1. @sferik

    Prep for release 0.4.1

    sferik committed Feb 12, 2013
  2. @scosman @sferik

    Possible fix for MySQL support

    scosman committed with sferik Feb 12, 2013
  3. @sferik

    Don't allow failure on Rubinius

    sferik committed Feb 12, 2013
  4. @sferik

    Test against JRuby

    sferik committed Feb 12, 2013
  5. @sferik
  6. @sferik

    Add Code Climate badge [ci skip]

    sferik committed Feb 12, 2013
  7. @sferik

    Add Gem Version badge [ci skip]

    sferik committed Feb 12, 2013
Commits on Feb 10, 2013
  1. @sferik

    Prep for release 0.4.0

    sferik committed Feb 10, 2013
  2. @sferik

    No need to check for Rails 3

    sferik committed Feb 10, 2013
  3. @sferik

    Merge pull request #26 from rwz/master

    Removed rails 2 compatibility
    sferik committed Feb 10, 2013
  4. @sferik

    Merge pull request #29 from scosman/master

    Perf suggestion
    sferik committed Feb 10, 2013
Commits on Feb 6, 2013
  1. @sferik

    Don't test against JRuby

    sferik committed Feb 6, 2013
  2. @sferik

    Specify minimum rspec version

    sferik committed Feb 6, 2013
Commits on Jan 29, 2013
  1. @scosman

    Even faster for postgresql

    scosman committed Jan 29, 2013
Commits on Jan 26, 2013
  1. @sferik

    Convert text files to Markdown

    sferik committed Jan 25, 2013
  2. @sferik

    Test against Ruby 2.0.0

    sferik committed Jan 25, 2013
Commits on Jan 25, 2013
  1. @scosman

    Fix the way we fetch jobs to work better for a large number of workers.

    Instead of fetching 5 candidates at attempting to lock each one by one, just lock the next job in 1 query.
    
    Example of old system and 100 workers (worst but not uncommon case):
    1) 100 workers wake up and fetch 5 candidate jobs (they all get the same, or very similar set of 5 jobs), making a total of 100 SELECT calls
    2) they all try to lock the first job (only 1 of 99 succeeds). The failing workers try the next, making a total of roughly 500 UPDATE calls
    3) a total of 5 jobs get processed from about 600 database calls, and we restart the whole process
    
    New system:
    1) 100 workers wake up and fetch the next available job, each getting a single unique job (1 SELECT and 1 UPDATE call each).
    2) a total of 100 jobs are processed with exactly 200 SQL calls
    
    I've also included an example to make it all work in 1 call, avoiding an extra round-trip. This requires custom SQL only tested with PostgreSQL
    scosman committed Jan 25, 2013
Commits on Dec 26, 2012
  1. @rwz

    Removed rails2 compatibility

    rwz committed Dec 26, 2012
Commits on Nov 29, 2012
  1. @albus522

    Fixed typo

    albus522 committed Nov 29, 2012
  2. @albus522
  3. @albus522
Commits on Nov 28, 2012
  1. @sferik

    Allow Rubinius failures

    sferik committed Nov 27, 2012
Commits on Nov 19, 2012
  1. @sferik

    Run specs in order to make them pass

    In the future, we should fix order dependency bugs.
    sferik committed Nov 19, 2012
Commits on Nov 18, 2012
  1. @sferik
  2. @sferik

    Fail fast

    sferik committed Nov 17, 2012
Commits on Nov 9, 2012
  1. @albus522
  2. @albus522

    Test rbx instead of rbx-2.0

    albus522 committed Nov 9, 2012
  3. @albus522
Commits on Nov 8, 2012
  1. @albus522
  2. @albus522

    Fix Travis status image

    albus522 committed Nov 8, 2012
Commits on Oct 10, 2012
  1. @sferik
Something went wrong with that request. Please try again.