Discussion: time specification for TPV

In the Small Scale Galaxy admin meeting we discussed how to specify runtime in TPV.

Currently the shared database does not consider time at all (as far as I see) - probably because not many (and in particular not the big instances) do need to specify time for job submission. But many instances need to specify the run-time for each and every job. The important point is that all of us have setups (using static job configs) that work reliably, but we want to switch to TPV because of its flexibility. On my instance I simply resubmit jobs if needed to destinations with 10min, 1day and 1week .. which works always but potentially wastes resources.

Adding absolute time values (in minutes, days, weeks, ...) probably makes only little sense since the local setups are too different (different compute generations, IO influence, ...). But on the other hand it would be better than nothing .. instances could define a scaling factor.

Ideas?