Quantcast
Channel: SCN : Unanswered Discussions - SAP Applications on SAP Adaptive Server Enterprise (SAP ASE)
Viewing all articles
Browse latest Browse all 809

Question about ASE 15.7 kernel mode – process vs threaded

$
0
0

Hi there,

 

This question is related to upgrading Sybase ASE Server
from version 15.5 to version 15.7 on Sun Solaris SPARC Operating System
(Solaris 10). For the upgrade, I need to choose between threaded kernel and
process kernel mode.

 

 

1> Is the process kernel mode in ASE 15.7 identical to
process kernel in ASE 15.5? Are there any changes to process kernel mode
between version 15.5 and 15.7? With all the other configurations on the Solaris
host being same (Number of CPUs, RAM, Storage, Sybase ASE Configuration
parameter values like total memory, engines), will the performance on ASE 15.7
in process kernel mode be same as on ASE 15.5?

 

If there are differences in performance, what are they? What should I be monitoring on ASE 15.7 to see

if there is performance issue on the ASE Server?

 

 

2> For the threaded kernel mode, are there any performance
overheads like more CPU usage? We are not planning to change the hardware
configuration of the Solaris host during the upgrade.  What values should I be monitoring at the OS
level OR Sybase ASE level to make sure that there are no performance issues? Is
there any particular parameter that needs to be monitored closely when we
change to threaded kernel mode?

 

Are there any Sybase Configuration parameters that I need
to tune for the New threaded kernel mode? If so, do you have any performance
tuning tips (white papers, technical documents) for threaded kernel mode?

 

 

3> What is SAP Sybase recommendation on which Kernel mode I
should be using? I researched the SAP Knowledge Base articles for
recommendations on which Kernel mode to use and I could not find a definitive answer.

 

 

Thanks,

 

Raj


Viewing all articles
Browse latest Browse all 809

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>