-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nuzzi wrote: > It is woefully slow.
A transaction requires two syncs (ie requesting the drive write the data to the metal and not return until it does). On average each sync will take a disk rotation so a 7200rpm drive maxes out at 60 transactions a second. If you require each data update to be physically on the disk then this is your limit no matter what library or storage mechanism you use. You can increase performance by increasing the number of updates per transaction. You can also do things like have an attached memory database and then flush its contents to the disk database every 5 seconds or whatever your tolerance for data loss is. You can also look at alternate storage mechanisms. For example rotating drives can be paired with a battery backed controller, or solid state could be used if the wear leveling and write-erase performance meet your needs. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmxqr0ACgkQmOOfHg372QR36ACgzApBSzqB3fW5lxgyAQaQjjn1 CaoAoNJ3nXrflO/QVZtNYlDFIfzgbLsO =n2sS -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
