oracle performance on solaris 8 Post: 31174

Sponsored Content

Special Forums UNIX Desktop Questions & Answers oracle performance on solaris 8 Post 31174 by Perderabo on Sunday 3rd of November 2002 11:08:58 AM

11-03-2002

Administrator Emeritus

First, see this post. Depending on which version of Solaris you are running, you may need to patch and/or tune your kernel to enable the priority paging option. And notice that one source I quoted in that post says that a 300% improvement *is* possible with this option on some versions of Solaris.

Now on to your next question. First, you should have your oracle databases on raw disk space, not in any filesystem. Oracle will tell you the same thing. Putting a database in a filesystem is guaranteed to slow it down. A lot! This may also render it unreliable.

There is a tunefs command that can tune an existing ufs filesystem, but it is limited it what is can tune. Any what tuning is does will not impact existing files unless you unload and reload them. If you going to do that, you may as well rebuild the filesystem from scratch which opens up more tuning options.

The ufs filesystem handles a mix of files very well. It's weakness is very large files. The absolute worst case is one file that consumes the entire filesystem. What makes a file "large" or not is whether or not it can reside entirely in one cylinder group. Increasing the size of cylinder group makes ufs lean more towards handles a few large files very well. Smaller cylinder groups makes it lean towards handling small files distributed in many directories well. If you have a few large files, large cylinder groups may help enough that you notice. On Solaris, the default is 16 cylinders per cylinder group. The best you can do is double that. The other thing is the "-o space" option. If you pick "-o time", Solaris will spend less time picking a new block when the file grows, at the cost of perhaps making a poor choice. You will pay for that each time you read the file. If you pick "-o space", Solaris will spend more time allocating a new block when the file grows. But you get a file that's easier to read. These are the two things that might be most worth persuing. I know I got burned when I said this about kernel tuning, but massive improvments are going to be very rare. Expect only marginal results.

Another option is the veritas filesystem. It is extent based rather than block based. It will handle very large files almost as well as it handles small files. I think it's a seperate product though with Suns.

Perderabo

View Public Profile for Perderabo

Find all posts by Perderabo

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Oracle-performance tuning

Sorry, This is out of scope of this group.But I require the clarification pretty urgently. My Oracle database is parallely enabled. Still,in a particular table queries do not work "parallely" always. How is this?

2. AIX

Oracle performance optimum vs. SGA memory allocation

Dear all experts, I have a p750 Power 7 3.3GHz server with 4 processors and 48GB Memory. This is a DB server which is using Oracle 9i. I have been told that Oracle 9i can only allocate 10GB as SGA Max to get the oracle optimum performance. Anything more will result in overflow of memory and will...

LEARN ABOUT BSD

install-solaris

install-solaris(1M)													       install-solaris(1M)

NAME

       install-solaris - install the Solaris operating system

SYNOPSIS

       install-solaris

       install-solaris	invokes  the  Solaris  Install	program. Depending on graphical capability and available memory at the time of invocation,
       install-solaris invokes either a text-based installer or a graphical installer.

       The following minimum requirements for physical memory dictate which features are available during installation:

       For SPARC machines:

       128 MB

	   Minimum physical memory for all installation types

       128 MB

	   Minimum physical memory required for windowing system

       384 MB

	   Minimum physical memory required for graphical-based installation

       For x86 machines:

       256 MB

	   Minimum physical memory for all installation types

       256 MB

	   Minimum physical memory required for windowing system

       512 MB

	   Minimum physical memory required for graphical-based installation

       In some cases, even if the minimum physical memory is present, available virtual memory after system startup can limit the number  of  fea-
       tures available.

       install-solaris	exists	only  on  the Solaris installation media (CD or DVD) and should be invoked only from there. Refer to the  for more
       details.

       install-solaris allows installation of the operating system onto any standalone system. install-solaris loads the software available on the
       installation media. Refer to the  for disk space requirements.

       Refer to the  for more information on the various menus and selections.

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcdrom  (Solaris instal-  |
       |			     |lation media)		   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Evolving			   |
       +-----------------------------+-----------------------------+

       pkginfo(1), install(1M), pkgadd(1M), attributes(5)

       It is advisable to exit install-solaris by means of the exit options in the install-solaris menus.

								    23 Sep 2005 					       install-solaris(1M)