Unix/Linux Go Back    

Solaris The Solaris Operating System, usually known simply as Solaris, is a Unix-based operating system introduced by Sun Microsystems. The Solaris OS is now owned by Oracle.

Solaris 11 performance optimization tips


Thread Tools Search this Thread Display Modes
Old Unix and Linux 01-09-2017   -   Original Discussion by bhavin1
bhavin1's Unix or Linux Image
bhavin1 bhavin1 is offline
Registered User
Join Date: Jan 2017
Last Activity: 9 January 2017, 11:33 AM EST
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Solaris 11 performance optimization tips


I need general tips for solaris 11 performance optimization.

For example - disable the unused services, etc.

Sponsored Links
Old Unix and Linux 01-09-2017   -   Original Discussion by bhavin1
rbatte1's Unix or Linux Image
rbatte1 rbatte1 is offline Forum Staff  
Root armed
Join Date: Jun 2007
Last Activity: 23 January 2018, 6:47 AM EST
Location: Lancashire, UK
Posts: 3,445
Thanks: 1,494
Thanked 673 Times in 606 Posts
Wow, where to start! Linux What hardware are you thinking of for your server - physical or virtual?

You need to know what your server will be doing and size it appropriately, so without over-purchasing (can be very expensive) you need to for on memory, CPUs and disk.

You are looking for a score-draw here, i.e. just enough without spending too much. Too much is a waste. Too little physical memory can leave your server needing to use virtual memory (aka paging or swap space) where memory addresses not currently needed are written to disk until they are needed again. This is a relatively slow process, so you have to justify on a business case how much to buy.

You are again looking for a score-draw here so that you have a chunk (not a very technical description) more than enough so that during peaks of processing, you don't plateau your CPU at 100%. You need to consider CPU speeds, quantity and number of cores per CPU. Again, it depends on what budget you have and justifying the cost against business need.

A controversial one this, disk can be considered in several ways.
  • Space - Is it relatively trivial amounts of data (say less than 300G total) or medium, large, huge or massive (typically over 5Tb) It depends on your definition as to what category you fit into.
  • Type - Solid state can be very fast, but is expensive
  • Disk - i.e. spinning media much cheaper, but slower. Mean time between disk failures is often over 10 years
  • Local JBOD - the server owns the disks and is directly responsible for everything they do. Can be slow, but cheap for smaller installations. You need to consider how to protect yourself from a disk failure.
  • Local RAID - the server owns the disks, but some responsibility is passed to a hardware controller so it can be configured to be fault tolerant. See Standard RAID levels - Wikipedia for information about RAID configurations.
  • SAN LUNs - Storage Area Network Logical UNits. For larger installations, this is much more usual. The SAN is usually multi-path fibre connected for resilience and the SAN contains a large amount of cache so that writes to disk appear to be very fast and the SAN completes the real write in it's own time. More expensive and more to manage, the disk can be shared between servers and can be replicated across sites, cities, countries or even continents if required (given enough network resource) This can give excellent fault tolerance, but is not a substitute for backups (errors will be replicated too)
  • Real disks or a volume manager? Real disks are arguably slightly faster but volume managers allow flexibility in disk layout, mirroring (if you are on Local JBOD) and the ability to copy data, make snapshots for backups and move data between disks/arrays/SANs
  • Disk layout
    • Generally you should look to separate /, /home (OS home area), /usr, /var, /tmp & swap space. Try to keep the boot disk used as little as possible. Just include the bare minimum to get the server running with the backup agent (if you have one)
    • Data, applications and user data (including their home area) is best kept away from the boot disk entirely. If you are using a volume manager, keep the OS in a separate volume group to everything else.

These are the main building blocks of your server. Way down on the list you should consider disabling unused services, however this is more of a hardening process to reduce your exposure to Denial of Service attacks or hacking attempts (even internal)

I hope that this gives you food for thought. I'm sure it's not an exhaustive list.

Kind regards,
Sponsored Links
Old Unix and Linux 01-09-2017   -   Original Discussion by bhavin1
jlliagre's Unix or Linux Image
jlliagre jlliagre is offline Forum Advisor  
ɹǝsn sıɹɐlos
Join Date: Dec 2007
Last Activity: 22 January 2018, 3:34 AM EST
Location: Outside Paris
Posts: 4,888
Thanks: 18
Thanked 641 Times in 559 Posts
A few comments, Solaris 11 is exclusively using ZFS for the system, so JBOD + ZFS mirroring is the recommended way to get performance and security (vs local hardware RAID). Snapshots is also a feature ZFS provides out of the box.

/var separation is the standard, /usr separation is not supported and would make the system unbootable as /bin is a symbolic link to /usr/bin.

Last edited by jlliagre; 01-09-2017 at 06:31 PM..
Sponsored Links

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Linux More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
solaris performance jegaraman Solaris 3 11-07-2011 04:01 PM
Solaris tips and tricks solaris_user Post Here to Contact Site Administrators and Moderators 1 09-24-2009 02:02 PM
tips Solaris chanfle Solaris 7 12-17-2007 05:47 AM

All times are GMT -4. The time now is 01:55 PM.