sybase thread model and cpu/core/thread at system level
I would like to have you feedback about the usage of sybase threads engines vs solaris chip/cpu/threads, if there are any settings that must be prevented.
as far as I understand, the sybase engines are now threaded (if configuration parameter 'kernel mode' is set to 'threaded' which is my case) meaning that at the system level we see only one process
my_host simon /tmp/
bash$ ps -ef | grep dataserver
s157 9192 9190 9 Apr 11 ? 1033:21 /my_host/sybase/ase157/MYHOST/ASE-15_0/bin/dataserver -d/my_host/sybase/ase157
bash$ prstat -L -p 9192
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/LWPID
9192 s157 95G 95G sleep 1 0 2:54:48 0.0% dataserver/22
9192 s157 95G 95G sleep 12 0 2:24:04 0.0% dataserver/20
9192 s157 95G 95G sleep 1 0 2:18:13 0.0% dataserver/19
9192 s157 95G 95G sleep 13 0 0:00:07 0.0% dataserver/1
Total: 1 processes, 276 lwps, load averages: 0.19, 0.43, 0.38
note: By the way is there a way to do the correlation between 'prstat -L' output and the 'number of max online engines'?
So we have threads at Sybase level
On the other hand, most servers I'm working on are Solaris10 zone and with those T6 processors, I have chip containing cores that could be multi-thread.
This means the output of mpstat shows the thread dedicated to my zone, I could potentially have to threads on the same chip etc...
are there any recommendations on how core/threads at system level should be configured for optimal performances? for example if my dataserver is configured for 4 threads, should I ask my UNIX admin to have a zone with 4 'virtual' cpu that are actually four threads on the same core?
Thanks for your input,