Maestro is slow to respond. Is there anything I can do?

There are many reasons that Maestro could be slow to respond: if it is reading structures over a network, or displaying over a network, for example, the slowness could be due to network response.

If you are using a release earlier than Suite 2011, Maestro can be slow to respond when you have a large number of jobs in the job database. Maestro checks periodically on the status of jobs, to update the Monitor panel, and this time can be significant when there are many jobs. You can use the jobcontrol command to purge the job database. For example, to delete all job records of completed jobs, you can use the following command:

$SCHRODINGER/jobcontrol -delete Status=completed

You can also set the default time interval after which completed jobs are automatically purged from the database in the environment variable SCHRODINGER_JOBDB_CLEANUP. The default is one week. For more information this setting and on job control, see the Job Control Guide.

The new job database format introduced in Suite 2011 should eliminate slowness due to large numbers of jobs.

Related Articles:

#1282: Maestro is slow to rotate structures. Is there anything I can do?
#1457: How can I optimize the performance of Maestro?
#208: Maestro is becoming slower and slower to start. What can I do?

Back to Search Results