As it is now job_get_next_job determines the next job to eval with a query that doesn't use any kind of index.

Added an index and made query use it :)

This needs to get on live soon if you ask me... As it is now, it takes 2-3 seconds to run one query on live and it is being run every 2 seconds by eval :)