[Swift-devel] throttling parameters with coasters
Allan Espinosa
aespinosa at cs.uchicago.edu
Tue Feb 24 18:52:29 CST 2009
In coasters, are throtte.submit, throttle.host.submit,
throttle.job.factor parameters ignored ?
Looking on how swift submits initial requests, it seems that
throttle.job.factor affects the number of coaster nodes it will submit
to the LRM. If I have
<profile namespace="karajan" key="initialScore">1</profile>
<profile namespace="karajan" key="jobThrottle">1</profile>
Swift spawns 4 coasters. 4*16=64 processors available to me. I
observe that throughout the job this number did not increase
Next, in my swift.properties, I have
throttle.submit=4
throttle.host.submit=2
But in the runtime,
rogress: Selecting site:2809 Submitting:17 Active:40 Stage out:31
Finished successfully:103
Progress: Selecting site:2809 Submitting:17 Active:40 Stage out:30 Finished su
so the 2 parameters does not apply to coaster submissions?
More information about the Swift-devel
mailing list