David Ressman

Hi Matthew, To be quite honest, Dan was the only person who was working on this. I have contributed next to nothing and just helped move the drmaa project to...

That seems pretty reasonable to me, provided the ability to subclass the subclasses to add site-specific options. (or some other reasonable way to do that).

In my experience, this, unfortunately, is very implementation-specific. In short, wallclock runtime is almost always required (and very important to the scheduling algorithm as you correctly note), but DRMAAv1 doesn't...

All the GE-derivatives I know of either a) refuse to schedule the job, and/or b) impose a default limit. My primary scheduler, for instance refuses to schedule the job: ```...

That said, I think you're allowed to set a default wallclock time of "0:0:0", which I think would be infinite, but it's still an explicitly set default time, if that...

This might be kind of a dumb question, but how well is dask able to predict _a priori_ the memory requirements of any task before the task is dispatched to...

This is a good question! This is a personal preference, but in my mind, I think it's entirely reasonable to keep it local, which would usually mean a login node...

I'll answer the last question first. Like with #4 , this can also get a bit site-specific. By default, every scheduler I know of will only request one core by...