Changes between Version 7 and Version 8 of JobQueue


Ignore:
Timestamp:
Nov 3, 2009, 12:15:35 AM (11 years ago)
Author:
Vincent Caron
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JobQueue

    v7 v8  
    3131
    3232hal:~$ pgrep -lf heavy_job
    33 10441 /usr/bin/heavy_job
     3310441 /usr/bin/heavy_job arg1
    3434
    3535hal:~$ jobq
     
    3838
    3939hal:~$ tail /var/log/user.log
    40 Oct 27 16:06:52 hal jobq: queue runner started for 'default' (pid 10421)
    41 Oct 27 16:06:52 hal job[10413]: start (delay:0 sec, todo:0): heavy_job arg1
    42 Oct 27 16:07:22 hal job[10413]: done (time:30 sec, exit:0)
    43 Oct 27 16:07:22 hal job[10447]: start (delay:23 sec, todo:0): heavy_job arg2 param2
    44 Oct 27 16:07:27 hal job[10447]: done (time:5 sec, exit:0)
     40Oct 27 16:06:52 hal jobq: queue runner started for user/queue 'foo/default' (pid 10421)
     41Oct 27 16:06:52 hal job[foo/default/10413]: start (delay:0 sec, todo:0): heavy_job arg1
     42Oct 27 16:07:22 hal job[foo/default/10413]: done (time:30 sec, exit:0)
     43Oct 27 16:07:22 hal job[foo/default/10447]: start (delay:23 sec, todo:0): heavy_job arg2 param2
     44Oct 27 16:07:27 hal job[foo/default/10447]: done (time:5 sec, exit:0)
    4545}}}
    4646
    47 Job 1 was scheduled and started at 16:06:52, and took 30 sec to complete.
     47First job was scheduled and started at 16:06:52 - taht is immediatly since queue was initially empty, and took 30 sec to complete.
    4848
    49 Job 2 was scheduled 7 secondes later at 16:06:59 (not logged), started at
     49Second job was scheduled 7 seconds later at 16:06:59 (not logged), started at
    505016:07:22 (23 sec after sheduling) and took 5 sec to complete.
    5151
     
    5757[[Image(jobq_effect.png)]]
    5858
    59 On Tuesday all jobs where run through a single queue by simply prepending 'jobq' to the existing commands in the crontab. The server was running smoothly again, and the problem was now a safer one where the job queue has to be monitored for not growing indefinitely.
     59On Tuesday all jobs where run through a single queue by simply prepending 'jobq' to the existing commands in the crontab. The server was running smoothly again, and the problem was now a safer one where the job queue has to be monitored for not growing indefinitely, searching for possible job parallelism and carefully creating new indepedent job queues.