This is an automated notification sent by LCG Savannah.
It relates to:
task #3195, project CDS Invenio
==============================================================================
LATEST MODIFICATIONS of task #3195:
==============================================================================
Update of task #3195 (project cdsware):
Should be Finished on: 2007-12-31 00:00 => 2008-07-01 00:00
Priority: 3 - Low => 6
Status: Postponed => None
Assigned to: None => skaplun
_______________________________________________________
Follow-up Comment #1:
At the same time, adding the possibility of tasks running concurrently. For
this an abstract idea could be:
each running task should update not only its current status and progress, but
an abstract concept of "task runtime description".
e.g. bibindex, once started, can declare on which indexes/records is working
on (at the beginning it could be any index/any record, but after the first
analysis it can definitively update its status) and go to sleep. If nothing
else should run, bibsched awake it and let it go. If another instance of e.g.
bibindex happens to work but on a set of records/indexes than the sleeping
bibindex can be awaken and let work concurrently. if there's a bibupload
correct instance that should run this can do the same. It discover on which
record it is going to run, and if these records are not also
indexed/corrected etc. by other tasks it can be awakened.
Bibsched would just require a checker function that checks whether two tasks
can run concurrently and decide accordingly.
==============================================================================
OVERVIEW of task #3195:
==============================================================================
URL:
<http://savannah.cern.ch/task/?3195>
Summary: Introduce priority management in BibSched
Project: CDS Invenio
Submitted by: jeanyves
Submitted on: 2006-03-27 09:29
Should Start On: 2007-03-01 00:00
Should be Finished on: 2008-07-01 00:00
Category: BibSched
Priority: 6
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: skaplun
Open/Closed: Open
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
Enable to launch a task with high priority that will interrupt current
running task and delay other tasks with minor priority
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: 2008-04-24 07:12 By: Samuele Kaplun <skaplun>
At the same time, adding the possibility of tasks running concurrently. For
this an abstract idea could be:
each running task should update not only its current status and progress, but
an abstract concept of "task runtime description".
e.g. bibindex, once started, can declare on which indexes/records is working
on (at the beginning it could be any index/any record, but after the first
analysis it can definitively update its status) and go to sleep. If nothing
else should run, bibsched awake it and let it go. If another instance of e.g.
bibindex happens to work but on a set of records/indexes than the sleeping
bibindex can be awaken and let work concurrently. if there's a bibupload
correct instance that should run this can do the same. It discover on which
record it is going to run, and if these records are not also
indexed/corrected etc. by other tasks it can be awakened.
Bibsched would just require a checker function that checks whether two tasks
can run concurrently and decide accordingly.
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
2195 | -COM-
1574 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?3195>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
