The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Agenda-16-05-2011"
| Line 12: | Line 12: | ||
==== 2.1 Workdir and tmpdir for parallel jobs ==== | ==== 2.1 Workdir and tmpdir for parallel jobs ==== | ||
The custom TMPDIR should be used also to solve the local disk throughput limits: with 16 or 32 cores the local disk can be stressed beyond its limit, and high performance network file systems have better performance. | [[Jobs wordir and tempdir]] | ||
Experiences from other site administrator on this topic performance '''are needed''' to consider solutions for this problem. | |||
New input from NGI_CH: Currently at CSCS the solutions in use are: ''CREAM JobWrapper'' and ''ARC custom submission scripts''. Those solutions are obviously middleware specific. | |||
The custom TMPDIR should be used also to solve the local disk throughput limits: with 16 or 32 cores the local disk can be stressed beyond its limit, and high performance network file systems have better performance. Experiences from other site administrator on this topic performance '''are needed''' to consider solutions for this problem. | |||
The customization of a job workdir should consider both the ''job type'' and the job ''disk performance requirements''. Can the second requirement be attached to the job submission? Is really needed? | The customization of a job workdir should consider both the ''job type'' and the job ''disk performance requirements''. Can the second requirement be attached to the job submission? Is really needed? | ||
Revision as of 10:10, 16 May 2011
Detailed agenda: Grid Operations Meeting 16 May 2011
1. Middleware releases and staged rollout
1.1. Update on the status of EMI-1 release (Cristina)
1.2. Staged Rollout (Mario)
1.4 Interoperability
2. Operational Issues
2.1 Workdir and tmpdir for parallel jobs
New input from NGI_CH: Currently at CSCS the solutions in use are: CREAM JobWrapper and ARC custom submission scripts. Those solutions are obviously middleware specific.
The custom TMPDIR should be used also to solve the local disk throughput limits: with 16 or 32 cores the local disk can be stressed beyond its limit, and high performance network file systems have better performance. Experiences from other site administrator on this topic performance are needed to consider solutions for this problem.
The customization of a job workdir should consider both the job type and the job disk performance requirements. Can the second requirement be attached to the job submission? Is really needed?
3. AOB
3.2 Next meeting
Proposal: Monday 23 of May 14:00