[go-nuts] Re: Task scheduler as a library?

2017-10-17 Thread Alex Buchanan
> > > Having tried using things like gleam/glow (see > https://github.com/chrislusf/gleam) and dask (which has similar ideas but > written in python) it sounds like a FIFO work stealing type scheduler > wouldn't be a bad idea. In particular dask's approach is quite nicely put > together.

[go-nuts] Re: Task scheduler as a library?

2017-10-17 Thread Jimmy Tang
On Monday, 16 October 2017 01:53:25 UTC+1, Alex Buchanan wrote: > > Not a spanner at all. > > I think the Task Execution Schemas (TES) [1], which Funnel is based on, is > a reinvention of DRMAA using technologies such as HTTP, REST, JSON, > Protobuf. It's a pretty simple API and message type

[go-nuts] Re: Task scheduler as a library?

2017-10-15 Thread Alex Buchanan
Not a spanner at all. I think the Task Execution Schemas (TES) [1], which Funnel is based on, is a reinvention of DRMAA using technologies such as HTTP, REST, JSON, Protobuf. It's a pretty simple API and message type (Task) for create, get, list, cancel. But, admittedly, I don't know enough

[go-nuts] Re: Task scheduler as a library?

2017-10-15 Thread Jimmy Tang
Not to throw a spanner into the works, but we have a similar problem in my work environment of needing a scheduler to schedule distributed jobs, one problem of writing a *nice* one for a given language is that you end up being pigeon holed into one solution. We've been looking at using drmaa as