vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| We have mutliple databases on our AIX test and development systems. Whenever we refresh a database all other users feel the impact of the process. Does anyone know how I can mimize the impact of this process so that CPU's and disk system resources are still available to other users. For example, the major bottleneck is disk IO. But if we use IBM's workload manager to keep the refresh process form monopolizing the disk system we find that the CPU's get adversely impacted with the result that they are mostly setting in wait state rather than doing useful work for other users. We want this refresh process to run at low priority in the background. I've tried "nice" and WLM. Both fail "Nice" has no impact because the disk system is monopolized; WLM frees up disk resources but sends all the processors into the wait state.. Next test is to try them together. But, I was wondering if someone on this list could give me some better ideas. I'm afraid I'm overlooking some of the other options I might have. Jeff Jacobsen |
| Thread Tools | |
| Display Modes | |
|
|