Hi,

Does anyone have experience to share about trying to get DATA_CACHE as high as 
possible on Solaris 8 (SunOS 5.8)?  I have a Sun Blade 1000 with 
8GB of RAM (64bit Sparc).  No other application is hosted on this system, only MaxDB 
for a single database instance.

I have no prior Solaris experience... started with a clean install of Solaris 8 and 
latest "cluster of patches".  MaxDB 7.5.00.08 failed due to problems 
creating the user account.  I got past that by manually running useradd.  I will do 
another post on that topic later.  As others have noted, the demo 
database fails to create if you don't increase seminfo values.

Experimenting with shmmaxshminfo_shmmax in /etc/system combined with data_cache.  
Observations so far:

1.  With 8GB of RAM, the most I have been able to set DATA_CACHE is 904397 (6.9GB) 
with the DEMO script.  I had shmmax set to 7750MB.  Solaris 
prstat shows MaxDB kernel using SIZE 7172M / RSS 7099M .  Any amount of DATA_CACHE 
more than 6.9 fails to create the TST database.

2.  Even with 904397 DATA_CACHE, I found that once I increased the size of the 
param_addvolume DATA to 14GB (1835008 pages) - SAPDB would fail 
in creating the database.  I had to decrease DATA_CACHE to 851968 (6.5GB) to clear 
this problem.

Looking for any tips I can get:  Basically only 3 users will be using this server for 
data analysis.  It will be read-only, no inserts.  Goal is to have as much 
of our DATA in memory as possible for nearly instant 'what if' style queries. 

# uname -a
SunOS cruncher1 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Blade-1000

Here is what I'm starting with on /etc/system additions:

set semsys:seminfo_semmap=9218
set semsys:seminfo_semmni=9216
set semsys:seminfo_semmns=18432
set semsys:seminfo_semmnu=8192
set semsys:seminfo_semume=160
set semsys:seminfo_semmsl=75
set semsys:seminfo_semopm=50
*  value  7900MB = 8283750400  (calculated by 1024*1024*7900).
set shmsys:shminfo_shmmax=8283750400
set shmsys:shminfo_shmmni=1024
set shmsys:shminfo_shmseg=256

P.S.  One thought that occurred to me.  Based on both my experience with Windows 2000 
DATA_CACHE and now experimenting with Solaris 8.... does 
the MaxDB "create database' require more RAM than an already-created database?  in 
other words... if I could create it with a lower value then change 
DATA_CACHE value _after_ install I may be able to get more of the RAM allocated to 
DATA_CACHE.  Have not tried yet... just wondering aloud.

Thank you.

  Stephen Gutknecht


---- Msg sent via @Mail - http://www.IPCoast.com/

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to