About this blog

As with my website, my blogs espouse the philosophy “not all performance problems are technical” and that in most stable environments user behaviour / usage patterns are typically the source of most correctable performance problems. So if you are into bits, bytes, locks, latches etc this is not the place for you, but if you are after ways to genuinely enhance performance and work with your systems and customers to achieve better, more predictable performance, read on.

Tuesday, May 15, 2012

Health tip #3 – Avoid having too many concurrent managers

Here we go again! After having written and blogged about this topic a fair bit in the past, having too many managers is a problem I still continue to see all too often. A good example is a site I worked with recently; it had 20+ managers just to run the workflow background processes.

Putting aside the need to address the excessive workflow background processes (which is another problem in its own right) there are major issues with the concurrent managers:

Problem #1 – Allowing 20 workflow background processes to run at once competes for the same resources on the same tables.

Problem #2 – Is one of basic queuing theory –i.e. 20 processes all competing for the same CPU and data resources.

In theory, 1 CPU handles 2 concurrent processes so in this case unless the site has 10 CPUs it runs the risk of CPU bottlenecking problems. The sting in the tail is these problems become most evident when you least need them to, like at high processing times such as month end.

What to do? It’s a simple choice. In this case identify why you think you need so many concurrent managers. You need to fix the cause and cut down on the number of managers, not just focus on the symptoms.

Want to know more? Take a look at the paper Concurrent Manager 101 & 202 on the website.  In fact there is heaps of FREE information and tips on all aspects of OEBS Applications Administration at so why not check it out!