Am 10.04.2013 20:54, schrieb Marc A. Pelletier:
On 04/10/2013 02:41 PM, Byrial Jensen wrote:
unless there is some option I can use to tell that.
What Tim mean is that, by default, SGE will schedule your job when sufficient resources are effectively available, rather that trying to predict when that will happen.
That said, you /can/ specify both a minimal starting time (with -a) and a deadline (with -dl) creating a "window" during which SGE will try to run your job but, in general, it's easier and more reliable to let the gridengine pick the time.
If your objective is to have your job run only when few others are trying to use the resources, you can also lower its priority (with -p) so that it will only execute your job when there isn't anything "better" to run.
-- Marc
If you are using sge you have not really care about. If you can use the hole cluster (linux and solaris) we mostly have enough capacity. It is only important that you can specify which resources (memory, runtime) you need.
If you need user database access on s3 you simple add -l sql-s3-user=1. If you rise the number of db-resources replag must be lower to get your job scheduled (e.g. -l sql-s3-user=3 currently gets only scheduled if replag is below 1 hour).
deadline option is not available on toolserver. -p mainly changes to priority compared to other jobs of yourself. For the global scheduling order job waiting time and used server resources by your user account in the last hours is more important.
Webserver requests which are also causing much database queries are high at 14-23 UTC workdays. Most sge jobs are submittet between 0-3 UTC.
Merlissimo