Michael Kleiser wrote :
>To test database-io-performance I executed this test-script:
>( Autocommit was off )
>select time from dual
>create table testtab (id integer, name varchar(200))
>commit
>insert into testtab (name) values ('ashd asdkjh sdkjhs dkajshd ')
>insert into testtab (name) select name from testtab
>...
>-- last line repeated 20 times, thats 2^20 records
>commit
>select time from dual
>This takes 3 minutes.
>On the same hardware (including same disk-array) I did the same with
>Oracle.
>This takes only 5 seconds.
>( I know, at this point of time oracle has write the changes only to
>it`s redo-logs. )
>( On a slower hardware I tryed it with PostgreSQL, it takes 18 seconds )
>When testing SAPdb, oracle was down and vice versa.
>Any suggestions to tune sapdb ?
>Compared to oracle, sapdb uses less SHM.
>Maybe this is the reason.
>Can this be changed ?
You should increase the parameter DATA_CACHE (SAPDB 7.3) or CACHE_SIZE (SAPDB 7.4)
respectively. This will help to keep a greater portion of the table in memory.
>On installation of SAPdb ( on Linux ) we choosed OLTP, because this
>use-case we intended to use SAPdb .
>If the tuning-solution is to insatll SAPdb as "live-cache",
>where there any implications for OLTP-applications ?
OLTP has been the right choice. Live-Cache is intended for SAP internal use only.
Best regards,
Thomas
--
Thomas Anhaus
SAP DB, SAP Labs Berlin
[EMAIL PROTECTED]
http://www.sapdb.org/
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
