The monq_task collection is quite busy; more write % than any other collection. With Mongo 2.2, moving it to a separate db will give it a separate write lock, which should help overall mongo performance.
err = db.getLastError();
forge:db/5105 Note the development.ini changes and make corresponding changes in your production.ini Then ensure that everything works for new events, and look for potential issues with tasks that are in-process during the deployment.
Log in to post a comment.