[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] memory leak in condor_q?

-stream-results is mostly of historical interest. At one time condor_q grabbed the entire job ad for each job and held all of the ads until it could sort them and print them out.

-stream-results was added when that was the case and it did save quite a bit of memory back then.

Now condor_q only fetches job attributes of interest to the specific condor_q query, so the memory savings of -stream-results is virtually non unless you also use -long.


On 2/6/2014 9:46 AM, Pek Daniel 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: