Some pieces of warning about "lock shared memory". This configuration option should only be activated when the whole machine has enough physical memory for all the applications to run smoothly. By reserving physical memory for ASE shared memory, ASE is reserving a large portion of memory at the expenses of the rest. If this will drive other applications to starve on memory, better don't let ASE be so greedy and either deactivate "lock shared memory" or decrease ASE's configured memory.
If the plan is to give to ASE 15 GB of a total of 16, better don´t lock ASE shared memory.
Also, if ASE shared memory is not locked and ASE is experiencing heavy paging activity, perhaps is better to reduce ASE's memory. It is an inefficient situation if ASE thinks there is some memory for her use but those memory pages have been paged out to swap files. It is better to configure only the memory that normal ASE activity will be able to reference often enough as to never be paged out by Solaris. Solaris will page out the oldest pages (old in terms of their last reference, no matter it is a read or a write) Too large a cache will cause some pages being too old, so possibly being paged out by Solaris. In this case, my advice is to shrink that cache.
Regards,
Mariano Corral Herranz