When you run one job at a time it takes about 40-45 sec. Here are the times for 5 users trying to import simultanously
no created started ended ended - started(sec) 1 11:59:16 11:59:22 12:00:02 40 2 11:59:16 11:59:30 12:00:40 70 3 11:59:16 11:59:45 12:01:17 92 4 11:59:16 11:59:42 12:03:07 205 5 11:59:16 11:59:36 12:04:20 284 Each job starts before the quickest one ends, but they wait for something just after parsing headers. Only one at a time is able to proceed import. They must have some shared resource they block when executing and that is probably the database. But is that how it supposed to be? Only one user is able to import RawBioAssay at a time and blocks the db for so long? 2007/10/31, Nicklas Nordborg <[EMAIL PROTECTED]>: > Paweł Sztromwasser wrote: > > > All job agents were configured to run all installed plugins and > > Everyone group has access to them. In fact each of them is able to run > > a job, but only if no other job is running. I saw couple of times (on > > JobAgents tab in web UI), as 4 of jobs were assigned to (let's say) 3 > > agents and only one was progressing. Others were at 0% progress with > > status 'Executing: parsing headers...'. When the progressing one > > If a job is listed as 'Executing...' it is running. So it seems that > your job agents have started more than one job after all. The status for > each job is only updated in intervals about 10 seconds. This may make it > seem like only one is progressing at a time. Especially if you have jobs > that doesn't take much time to execute. For example if they take less > than ten seconds the first status update will be 0% and the next 100%. > > If you check the started and ended time for each job you can get better > timings and also see if they actually overlap or not. > > /Nicklas > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > basedb-devel mailing list > basedb-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/basedb-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ basedb-devel mailing list basedb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/basedb-devel
