From: Knappke, Christian (christian.knappkesap.com)
Date: Wed Jul 02 2003 - 04:48:46 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> We've created a sapdb which handle 500 transations per second
> (combination of inserts/updates/deletes)
> it handles it for about 15-20 minutes and then freezes with no error
> messages. We've verified that we have not run out of disk space, dev
> space, log file space, memory and cpu usage.
>
> Is there a limitation on how many (simple -- no joins)
> transactions per second can be applied?

There is no limit ;-)

> We need to get it up to 2000 per second. We've
> only started testing with sapdb and have limited knowledge of
> the parameters.
>
> We're running on Sun Solaris with 14 cpu's and 14gb of
> memory.

How are the following parameters set?
  CACHE_SIZE (7.4) or DATA_CACHE (7.3)
  MAX_CPU
  MAX_USERTASKS
  MAX_LOCKS

Are other CPU intensive or memory intensive applications on the server?
How many CPUs are used by your application?
How many users are connected?
Do you run large insert/update/delete jobs in one single transaction?

> Has anybody gotten any results that we expect and if so, what parameters
> did you change and to what value?

If just the SAP DB and your application share the server mentioned, I'd start with
CACHE_SIZE/DATA_CACHE = 512000 (4GB)
MAX_CPU = 6

HTH
Christian

--
#include <std_disclaimer.h>
/* The opinions stated above are my own and not
   necessarily those of my employer. */
_______________________________________________
sapdb.general mailing list
sapdb.generallistserv.sap.com
http://listserv.sap.com/mailman/listinfo/sapdb.general

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]