emulator 1 Report post Posted October 2, 2009 I've noticed that in some instances, such as recycling large/complex backup sets, Retrospect only relies on one CPU core: http://images.morrispress.com/One_CPU_Used.jpg The above screenshot was taken when a backup set was being recycled, and it was running for over two hours! During that time, Retrospect cycled through CPU cores, but never really used more than one at a time. It seems to me that the software should be using more than one CPU core at a time, especially when the catalog recycles take hours and hours to complete. Share this post Link to post Share on other sites
mauricev 0 Report post Posted October 8, 2009 It might that you're seeing odd behavior. I generally see all the cores in relatively equal use and I've found performance to improve after I've assigned additional cores to my Retrospect instances. This is true even when using just one execution slot. Share this post Link to post Share on other sites
emulator 1 Report post Posted October 10, 2009 I generally see this only when a large backup set is being recycled. During this time, no other scripts can run and the interface is unusable. Share this post Link to post Share on other sites
