[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] best practices for data untar/unzip
- Date: Tue, 01 Nov 2016 14:29:43 +0000
- From: Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] best practices for data untar/unzip
This illustrates one of the problems of having started with UNIX in about 1985 - these newfangled contraptions like ionice don't spring to mind. Great idea, Thomas! On UNIX System III, we only had "nice" - and we liked it!
It also brings to mind the idea of switching off the kernel IO scheduler (set it to noop) if you have a write-caching RAID array controller. There's no sense having the Linux kernel waste CPU cycles sorting the disk writes when the RAID controller is going elevator sort everything anyway:
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Thomas Hartmann
Sent: Tuesday, November 01, 2016 6:35 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] best practices for data untar/unzip
just a shoot in the dark but maybe ionicing the tars could improve the situation?
Something like the best effort scheduler with a random priority so to avoid choking on all tars with the same low priority or maybe going for the idle scheduler (but no idea, how the grace period block would effect the overall performance)?