[Swift-devel] Re: several questions about coaster

Mihael Hategan hategan at mcs.anl.gov
Tue Apr 28 16:25:26 CDT 2009


On Tue, 2009-04-28 at 15:42 -0500, Zhao Zhang wrote:
> Hi, Mihael
> 
> Mihael Hategan wrote:
> What is the largest
> >>     scale test we have done with coaster? I mean the ratio between 
> >> coaster dispatcher and the number of workers.
> >>     
> >
> > Typical stuff on ranger. Around 1000 nodes.
> >   
> Btw, could coaster use all cores on a single compute node? I mean in a 
> multi-core context.

Using "coastersPerNode" attribute, yes.

> >   
> >> 2. Usability
> >>     All tests I have tried with coaster were running together with 
> >> swift. That is a black box test for me. Is there any interface in coaster
> >>     that I could specify the number of workers and the wall time?
> >>     
> >
> > Like all profile entries, they are task attributes.
> >
> >   
> >>     Also, is there a way for me to start coaster service and workers 
> >> separately and independently?
> >>     
> >
> > The coaster provider is a provider like any other. Use the "job
> > submission example" in cog and change the provider to "coaster".
> >   
> I found this link, but it is empty. 
> http://wiki.cogkit.org/wiki/Java_Cog_Kit_Examples_Guide#Job_Submission

Use
http://wiki.cogkit.org/wiki/Java_CoG_Kit_Abstraction_Guide#How_to_execute_a_remote_job_execution_task

> >   
> >>  If I run coaster in a super computer
> >>     context, can I ask coaster to hold a certain number of compute
> nodes 
> >> for a certain amount of time? (This somehow overlaps the first Q
> in 
> >> section 2)
> >>     
> >
> > You don't seem to have tuned in much into recent discussion on this
> > mailing list.
> >
> > No, you can't.
> >   
> I knew this from the discussion between you and Mike. So is this a 
> feature that we are going to implement soon, or we haven't decided?

It was the highest priority up until last night. Right now it isn't, so
I can't say when I think it will be done. I'll try to squeeze it in.





More information about the Swift-devel mailing list