Drake Diedrich writes: > In some tests I ran, I found that postgres was only capable of 4 > transactions per second in the default configuration. The speed could be > increased to 80 transactions/sec if you were willing to turn off the > automatic disk syncing. It is not clear from the mysql documentation > whether it syncs the disk after each transaction, so mysql may only be > comparable to the unsync'd postgres speed. With an fsync after each > transaction, Postgres is limited by disk seek times. You might be able to > speed it up by putting each file in the database on separate (fast) disks.
No DBMS syncy after each transaction. Most systems do it every 30 seconds. Support for that will be added to Postgres later on. And with 80 TPS I think Postgres is doing quite a job. I remember some co-workers timing Oracle on an SCO machine a while ago. With a huge database it wasn't able to do more than 50 TPS. Michael -- Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH [EMAIL PROTECTED] | Europark A2, Adenauerstr. 20 [EMAIL PROTECTED] | 52146 Wuerselen Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44 Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
