Are the internal database maintanance cycles tuneable or running in a low priority so they don't take over system resources? IHAC who is asking because they have experienced system performance degradation in 4.0.x due to this.
Unfortunately I can't get that information, this is all word of mouth from the customer and they are now on OnCommand 5.0 beta and wondering if they will experience the same issue, hard to answer without any quantifiableback ground information, what MIGHT cause the behaviour?
