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

Re: [Condor-users] GCB Performance



Chris Miles wrote:
Ok. The condor pool is made up off exactly the same spec machines. Its an IBM Cluster.

I firstly ran a test to see how long my 50 jobs would take on just one machine (2 VMs)
and it took 5m 11s
I then loaded up 10 nodes -- Jobs took 2m 8s
I then loaded up 20 nodes -- Jobs took 2m 22s

I think I also figured out why 20 nodes were slower than 10 nodes. The reason might be another configuration issue. In the experiment with 20 nodes but not with 10 nodes, there was 20sec delay between job submission and match notification from the negotiator. By default, Condor puts 20sec delay between negotiation cycle. Please look for NEGOTIATOR_CYCLE_DELAY variable in the manual. So, seems like you did "20 nodes" experiment within this 20 sec delay and that made 20 nodes slower than 10 nodes.

I don't believe how you did your experiment. However, I don't believe that it is a good idea to evaluate GCB performance by measuring time between submitting jobs and their completions. So many things and coincidences affect the performance. If you are measuring Condor performance, I would recommend you to talk with Miron.

Find attached are the logs for the submission machine from the 10 and 20 node tests.
thanks
Chris