Yesterday we pushed out a new deployment with a number of updates. We updated our version of the jQuery Javascript library, so for free we got several improvements to things like the tables we use to display data throughout the system. Eric also made some performance improvements to the job explorer page, and added a feature where if you select two solvers in the solver summary part of the job explorer page, you get a new button which lets you compare those two solvers head to head. This is a feature requested by Clark Barrett. Finally, we added a feature where we (the administrators) can set different max timeouts for different queues. Currently all.q and all2.q have wallclock timeout set for 1 hour (and CPU timeout for 4 hours). I added long.q with currently 15 nodes, for longer-running job pairs. The max timeout is 12 hours. Feedback on these decisions is welcome.
 | martina.seidl on Redeployed now, crossing … |
 | timothyalanking on Redeployed now, crossing … |
 | aaron.stump on We are redeploying this a… |
 | David on We are redeploying this a… |
 | Clark Barrett on Fighting a db connection … |
StarExec 
Leave a comment