On Sonntag, 20. Juli 2008 18:19:57 Ioan Raicu wrote: > Hi, > You are forgetting that in real Grid deployments, the majority of the > wait time will be in queue wait times in batch schedulers. For example, > in some logs I looked at from 2005 from SDSC, I recall seeing queue wait > times of 6 hours on average over a 1 year period. So, having some extra > latency on the order of 1~60 seconds is not a big deal when your average > job lengths are hours, or more.
This might be write for your usecase. However, there are also other usecases around in the grid world. We are running [EMAIL PROTECTED] as a task farming application on the ressourece of D-Grid, and we consume per day about 100000 CPU hours. So it is really a productive application. Because we are submitting hundred of jobs, the latency cannot be neglected, and it wold be really helpful to reduce it to a time below 1 second. If you're looking into the net traffic caused by globusrun-ws -submit, you can see thereare a lot of communication cicles (I think it are 9) between the submitting and the execution host. Is this really necessary? SOAP only requires one... So please note: there is no "real Grid deployment" in that way, you've mentioned it. I think this problem will get still more bothersome, if a scheduler as e.g. Gridway is coming into the game. Cheers Alexander
