On Fri, 10 Mar 2006, Marco Mambelli wrote:
In a VDT installation un a linux machine is it normal to have
condor_history taking more than 2 min to answer?
That is about how long mine takes with condor-6.7.13. It depends
on how busy your schedd is at the moment, how many jobs in the queue, etc.
#time condor_history 173517.0
((ClusterId == 173517) && (ProcId == 0))
ID OWNER SUBMITTED RUN_TIME ST COMPLETED CMD
173517.0 usatlas1 3/8 11:13 0+00:05:18 X ??? /home/usatlas1/
real 2m37.079s
user 2m29.360s
sys 0m0.720s
The condor history file is big but not huge:
-rwxr-xr-x 1 root root 663080 Jul 14 2005
/opt/condor-6.7.9/bin/condor_history
that's the binary. Actual history file lives in $LOCAL_DIR/spool/history.
450MB for my cluster and we have been up about a year on the
same history file.
Steve
I know that quill may be a solution. condor_history is rarely used, only
for debugging. Was just curios about which response time I should expect.
Thanks,
Marco
_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/condor-users