Hi alpmoon,
Only two sybase processes are very active and the other sybase processes consumes 2% to 3% CPU. The value of the context switch is not large when the users report slow response.
I will move the most sybase process to a new AIX server but in the meantime I have to resolve the slow response problem. Do you have interium solution to resolve the performance issue. Right now we re-schedule all non-ciritical batch processing of another sybase to non-peak hours and the performance is improved. However we cannot stop the users of other sybase to do on-line processing (ie enquiry or update
<<<
CPU usage can be restricted based on application etc
>>>
How can I restrict a sybase application to use CPU?
cpc
Main Topics
Browse All Topics





by: alpmoonPosted on 2006-03-05 at 17:24:39ID: 16110650
As much as I understand you have 4 Sybase instances (dataservers) on a two CPU UNIX box. If these four Sybase instances are active most of the time, it is not a good idea at all. You see a high kernel usage because UNIX needs to switch process context all the time. Also it looks SybaseA is active all the time (CPU usage is 50 per cent).
I suggest either to add another two CPU's or to consolidate all databases in two Sybase instances (or one if it is possible). Maybe you should find out why there are four Sybase instances first.
Sybase is different than Oracle in terms of the relation between server instances and databases. You can create many databases in the same Sybase instance. Most of the cases, it is much better than creating one Sybase instance for each database. Sybase has many features to allocate resources for a particular database. You can create named data caches and bind them to a particular database. CPU usage can be restricted based on application etc.