Reuti <[email protected]> writes: > Hi, > > Am 20.03.2013 um 15:58 schrieb Lars van der bijl: > >> hey everyone, >> >> a few weeks ago we where having issue with users submitting jobs the >> did massive IO to the file system. each task was writing out about 4 >> GB of data and reading in about 2GB. as this was happening in >> parallel from our farm it brought our server to it knee's and cause >> people to moan like crazy.
Ensure the (network file?) server is tuned properly. We cope with array jobs doing that sort of thing to NFS. >> I'm I right in thinking that the IO output of a job would help me >> detect the tasks disk IO? Local or networked? >> I can't seem to find any good information on what the qstat IO output >> means. I remember seeing that it has something to do with Gb/s ? It should be labelled "GB". > In case you refer to the field which is also listed in `qacct -j > <jobid>`: [I.e. cross-referenced from qstat(1). It probably needs better explanation of other bits of output.] > `man accouting` > > http://arc.liv.ac.uk/SGE/htmlman/htmlman5/accounting.html -- Community Grid Engine: http://arc.liv.ac.uk/SGE/ _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
