Today on this ol' server

Resource Management on Solaris 10 and beyond

At the last Opensolaris Silicon valley user group meeting, Ben Rockwood lamented how hard it is to understand resource management.

That reminded me of how I really had to read through the docs and play with the commands to get the tunings right. In this forum post I explained how to set the tunings needed for DB2 at the time of the forum post.

A few key concepts can help with tunings:

• check that you really need to tune. If you're running the latest and greatest OS build, chances are the tunings are right, or if your hardware is sufficient large, the default tunings will be sized up, and should be correct for most apps.
• beware of documention that says add this setting to /etc/system. /etc/system isn't used in Solaris 10 and beyond for managing most resources. (There are some bug fixes, that can only be set in /etc/system.) Most resource tuning and tweaking can only happen by resource management commands, prjadd(1M), projmod(1M), project(4), rctladm(1M), setrctl(2), prctl(1)
• Always use the documentation that came with the specific OS version you're running. The tunings vary from releases, the what's new, and Tunable Parameters Reference Manual will have the most accurate instructions.
• Some tunings can be set on a per project basis others are set on a per process basis, but is inherited by user per project.
• When in doubt test: use newtask -p project id name command, and check the resource tunings with prctl.

  bash-3.00$ newtask -p myproject sleep 100 &
  bash-3.00$ prctl $!
  [1] 14027
  process: 14027: sleep 100
  NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT
  process.max-port-events
          privileged      65.5K       -   deny                                 -
  ...
  

Posted at 12:46AM Jan 29, 2007 by saf in Sun  |  Comments[1]