List:MaxDB« Previous MessageNext Message »
From:Martin Brunzema Date:September 30 2002 2:23pm
Subject:RE: SAP DB vs MS SQL Performance
View as plain text  
> The question is why M$ SQL (173,609ms)  is twice fast than SAPDB (319,399ms)
> to insert 10,000 64 byte record. I am not sure JDBC drive play what kind of role
> this
> performance. One thing I notice is JDBC drive for SAPDB take 150ms than to load than

Maybe the insertion will result in a hot spot. E.g. if you insert
small records at the end of a table, then the last page has to be
locked. This leads to a serialization of the insertions. In this
case there is no benefit from the multiprocessor architecture.

> Mircrosoft JDBC driver.  I used default configuration for M$ SQL. The SAPDB 
> configuration is used the one from the website. Here is the configuration parameters.
> 
> 
> param_rmfile
> param_startsession
> param_init OLTP
> param_put MAXCPU 4
> param_put DATA_CACHE 16384


Datacache is the size of the memory used to cache data pages.
You reserved 16384 pages of 8K size => 128 MB memgory in a 2 Gigabyte-
machine. (But if you insert only 10,000 * 64 Byte this should not
really matter ;-)

Martin

Thread
SAP DB vs MS SQL PerformanceXT Wang28 Sep
  • Re: SAP DB vs MS SQL Performancedetlef schulze30 Sep
    • RE: SAP DB vs MS SQL PerformanceDirk Ringe30 Sep
RE: SAP DB vs MS SQL PerformanceSAPDB)29 Sep
  • RE: SAP DB vs MS SQL PerformanceXT Wang29 Sep
RE: SAP DB vs MS SQL PerformanceSAPDB)29 Sep
  • RE: SAP DB vs MS SQL PerformanceXT Wang29 Sep
RE: SAP DB vs MS SQL PerformanceMartin Brunzema30 Sep
RE: SAP DB vs MS SQL PerformanceXT Wang7 Oct
  • RE: SAP DB vs MS SQL PerformancanceRichard Barrington7 Oct