[Swift-user] job waiting
Yue, Chen - BMD
yuechen at bsd.uchicago.edu
Tue Apr 21 10:53:02 CDT 2009
Hi Ben and Mihael,
Thanks for answering my questions. I will try to set the maxwalltime in tc.data in my application and let you know how it works.
My Swift installation is at /home/yuechen/swift-0.8 on Communicado. Please let me know if you see any problem in my setup.
Thank you very much!
From: Mihael Hategan [mailto:hategan at mcs.anl.gov]
Sent: Sun 4/19/2009 11:20 AM
To: Ben Clifford
Cc: Yue, Chen - BMD; swift user
Subject: RE: [Swift-user] job waiting
On Sun, 2009-04-19 at 07:07 +0000, Ben Clifford wrote:
> On Sat, 18 Apr 2009, Yue, Chen - BMD wrote:
> > Thanks for answering my question. This phenomena occur after half an
> > hour of execution. If all the jobs finish execution at original speed,
> > it would probably take not more than 40 min. How the system figure out
> > that some jobs will take more than 1 hour? Should I request more time
> > when I execute "grid-proxy-init"?
> Not with grid-proxy-init. You can specify a parameter called maxwalltime
> in your sites file or your tc.data file that will tell Swift an upper
> bound on how long your job will run. In Swift 0.8, coasters assume
> something like 10 minutes if you do not specify a walltime, so you will
> run into trouble.
> For example, change the null at the end of your tc.data lines to
> globus::maxwalltime=50 to mean 50 minutes maxwalltime.
> There has been work done on coasters since Swift 0.8, and so Mihael may
> have some other recommendations.
Yes. Coasters are experimental. As such, there are problems. However,
you may get better results with the current development version.
> > I did not change the default throttles. How much is more appropriate?
> > The total number of jobs in my application typically run between 4000
> > and 30000 and typically each job can be finished within a couple of
> > minutes.
> Where is your Swift installation? I would liek to look at it.
This email is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this email message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is prohibited. If you have received this email in error, please notify the sender and destroy/delete all copies of the transmittal. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Swift-user