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

Re: [HTCondor-users] Soap API

We used it for a while, but for our purposes it turned out to be way too slow. Jobs were taking somewhere around 0.1 seconds per process to submit, so a 100 process job took almost 10 seconds to submit. Now, due to some database calls that were going on in our submission code, this probably could have been cut in half, if not further, and this may be sufficient for your purposes.

However, we just recently switched to using Python-Condor, which sidesteps the major bottlenecks that occur with SOAP.
(Just for reference, I get about 0.0009 sec/process with python-condor.)

But it really depends on your situation. If super-quick job submission speed isn't a requirement or your jobs aren't very large, then SOAP will probably work just fine for you.

On Wed, Feb 27, 2013 at 12:10 PM, Guy Schwartz <guy.rslab@xxxxxxxxx> wrote:

I've been using the soap API for a while now and I'm pretty happy.
Does anyone know how stable is it? what stress can it hold?

Did anyone ever did a performance test on this service?

Just wondering if I write software that will communicate heavily with
condor by using soap, if this service will hold...

Is it a better way to communicate with condor? each program i seen on the web usually calls
the CLI commands and parse the outputs... looks inefficient to me.

Any thoughts?



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: