Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
System Administrator Guide for CREAM for EMI-1 release
| ||||||||
Changed: | ||||||||
< < | 1 Installation and Configuration | |||||||
> > | 1 Installation and Configurationf | |||||||
0.1 Prerequisites | ||||||||
Line: 665 to 665 | ||||||||
To allow a parallelism when interacting with the batch system, in particular to have a good throughput when submitting jobs to the batch system, CREAM can run multiple BLAH instances. A new instance is created whenever needed, till the maximum number defined in the etc/glite-ce-cream/cream-config.xml configuration file is reached. The relevant attribute is cream_concurrency_level . The default value is 50. | ||||||||
Added: | ||||||||
> > | 0.0.0.1 Tune the BLAH BUpdater polling frequencyIf the new BLAH Blparser is used (click here for instructions to check if you are using the old or the new blparser) the parameterbupdater_loop_interval attribute in /etc/blah.config defines how often the batch system is queried to check the status of the jobs. If a low value is used, job status changes are detected promptly, but this also means that several batch system queries are done, and this can cause a high load.
With yaim-cream-ce v >= 4.2.2-1, this parameter is configurable via yaim: the relevant yaim variable is BUPDATER_LOOP_INTERVAL which has 30 (secs) as default value.
With yaim-cream-ce v. < 4.2.2-1, this parameter is not configurable via yaim, and therefore it is needed to manually edit the blah configuration file, otherwise the default value (5 s.) is used.
After having set this value in the blah configuration file it is necessary:
bhist -u all -d -l -n 1 ).
| |||||||
1 Postconfiguration |