In addition to the suggestions above I would look at the memory usage pattern while the IO is going on
watch cat /proc/meminfo This system might have a decent amount of memory - but are the sysctl tunings for the dirty buffer sizes set small or something? On 2 August 2014 04:17, Chris Samuel <[email protected]> wrote: > On Fri, 1 Aug 2014 03:13:39 PM mathog wrote: > > > That may fix the problem but I am still curious about exactly what > > happened during the terminal stalls. Using the current cfq scheduler > > what is going on in the system that is keeping those terminal processes > > from getting any CPU time? > > Not entirely sure, but you may get some idea with latencytop *if* it is > able > to get some time to run to return info. > > cheers, > Chris > -- > Christopher Samuel Senior Systems Administrator > VLSCI - Victorian Life Sciences Computation Initiative > Email: [email protected] Phone: +61 (0)3 903 55545 > http://www.vlsci.org.au/ http://twitter.com/vlsci > > _______________________________________________ > Beowulf mailing list, [email protected] sponsored by Penguin Computing > To change your subscription (digest mode or unsubscribe) visit > http://www.beowulf.org/mailman/listinfo/beowulf >
_______________________________________________ Beowulf mailing list, [email protected] sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
