[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] memory leak in condor_q?
- Date: Thu, 6 Feb 2014 10:06:36 -0600
- From: Brian Bockelman <bbockelm@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] memory leak in condor_q?
This is expected. Stream does not stream (well, until my patches land). It still buffers the entire response in memory before parsing it.
Stream prevents HTCondor from sorting the results in memory.
Non-blocking condor_q patch set will take care of this and turn it into a real stream.
Sent from my iPhone
> On Feb 6, 2014, at 9:46 AM, Pek Daniel <pekdaniel@xxxxxxxxx> wrote:
> I've noticed there's not so much difference between the memory
> consumption of condor_q -stream and condor_q:
> [root@XXX thrash]# /usr/bin/time -v condor_q -stream >/dev/null
> Maximum resident set size (kbytes): 186592
> [root@XXX thrash]# /usr/bin/time -v condor_q >/dev/null
> Maximum resident set size (kbytes): 306352
> There was 100k jobs in the queue. I've dug into the source a bit, and
> I suspect some leak somewhere here:
> or here:
> Maybe the ReliSock, or the ClassAd...
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: