Den 10-04-2013 20:06, Tim Landscheidt skrev: Well, no. SGE cannot know if I want the job run as early as possible or if I can happily wait for several hours for a less busy part of the day, unless there is some option I can use to tell that.

Am 10.04.2013 20:54, schrieb Marc A. Pelletier: 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

Den 10-04-2013 21:35, Merlissimo skrev: Thank you for the explanations to all. They could be used to improve the documentaion for SGE. BTW I can use the whole cluster, as I made this little script to start my compiled C programs: #!/bin/sh ARCH=`uname` PROG=$1 shift /home/byrial/bin/$ARCH/$PROG $@

On 04/10/2013 07:51 PM, Tim Landscheidt wrote: I wasn't sure you were talking to me. :-) Icinga have graphs, but they're uptime-related. The place with the pretty graphics is ganglia: http://ganglia.wmflabs.org/latest/?c=tools But there is no queued/running job graph right now. It's a very good idea though, and I'll add the matching instrumentation. -- Marc