Hello Dilek, you can of course increase the parameter CACHE_SIZE if the hit rate is low, and you fear that the size is too small. It should however be in the limits of the physical memory available on that machine, to make really sense.
However, as you said you have queries not using indexes to reduce the number of records that need to be read to evaluate the qualification, you'd better look whether these queries can be modified to avoid the table scan at all, and go for a better strategy. Regards Alexander Schr�der SAP DB, SAP Labs Berlin > -----Original Message----- > From: dilek.ciplak [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 04, 2004 3:32 PM > To: [EMAIL PROTECTED] > Subject: how to determine sapdb cache_size? > > we have sapdb 7.4 running with jboss on win xp server having 1GB RAM. > > as you already know cache_size is the most critical parameter in sapdb > > we decided to give min 128MB, max 512MB for jboss > > set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -Xmn128m > -Xmx512m set JBOSS_HOME=%DIRNAME%\.. > > and thougt that it would be enough to separate 160MB to sapdb > cache 40000 (4K each page) totallly > > cache_size=160 MB > > but for tables having more than 300.000 rows our queries do > not use the index that must certainly be used and do table > scans whic means > the reports running these queries long last > > is it possible (logical) to increase the cache_size? > > thanks a lot > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
