Re: Share GPU resources via attributes or as custom resources (INTERNAL)

2016-01-19 Thread Benjamin Mahler
nd out design proposal to community >> for comments. >> >> >> >> Regards >> >> -- >> Vikram >> >> >> >> *From:* Benjamin Mahler [mailto:bmah...@apache.org] >> *Sent:* Saturday, January 16, 2016 4:31 PM >> *To:* user@meso

RE: Share GPU resources via attributes or as custom resources (INTERNAL)

2016-01-18 Thread Vikrama Ditya
better job scheduling. As Ben indicated very soon we will send out design proposal to community for comments. Regards -- Vikram From: Benjamin Mahler [mailto:bmah...@apache.org] Sent: Saturday, January 16, 2016 4:31 PM To: user@mesos.apache.org Subject: Re: Share GPU resources via attributes

Re: Share GPU resources via attributes or as custom resources (INTERNAL)

2016-01-16 Thread Benjamin Mahler
There is a design proposal coming that will include guidance around using GPUs and better GPU support in mesos, so stay tuned. Mesos supports adding arbitrary resources, e.g. --resources=cpus(*):4;gpus(*):4 Mesos will then manage a scalar "gpu" resource with a value of 4. This means "gpu"

Re: Share GPU resources via attributes or as custom resources (INTERNAL)

2016-01-15 Thread Klaus Ma
gt; *From:* haosdent [mailto:haosd...@gmail.com] > *Sent:* 14. januar 2016 19:07 > *To:* user > *Subject:* Re: Share GPU resources via attributes or as custom resources > (INTERNAL) > > > > >Then, if a job is sent to the machine when the 4 GPUs are already busy,

Re: Share GPU resources via attributes or as custom resources (INTERNAL)

2016-01-15 Thread Guangya Liu
riment with attributes. > > > > Cheers, > > Humberto > > > > > > > > *From:* haosdent [mailto:haosd...@gmail.com] > *Sent:* 14. januar 2016 19:07 > *To:* user > *Subject:* Re: Share GPU resources via attributes or as custom resources > (INTERNAL) >

RE: Share GPU resources via attributes or as custom resources (INTERNAL)

2016-01-15 Thread Humberto.Castejon
I guess I will have to experiment with attributes. Cheers, Humberto From: haosdent [mailto:haosd...@gmail.com] Sent: 14. januar 2016 19:07 To: user Subject: Re: Share GPU resources via attributes or as custom resources (INTERNAL) >Then, if a job is sent to the machine when the 4 GPUs are

Re: Share GPU resources via attributes or as custom resources (INTERNAL)

2016-01-14 Thread haosdent
>Then, if a job is sent to the machine when the 4 GPUs are already busy, the job will fail to start, right? I not sure this. But if job fail, Marathon would retry as you said. >a job is sent to the machine, all 4 GPUs will become busy If you specify your task only use 1 gpu in resources field. I

Share GPU resources via attributes or as custom resources (INTERNAL)

2016-01-14 Thread Humberto.Castejon
I have a machine with 4 GPUs and want to use Mesos+Marathon to schedule the jobs to be run in the machine. Each job will use maximum 1 GPU and sharing 1 GPU between small jobs would be ok. I know Mesos does not directly support GPUs, but it seems I might use custom resources or attributes to do