Hello! On Saturday 07 March 2009 01:59:13 Roger Binns wrote: > 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.
That's great description! Can you add this to documentation? I did know the limit experimentally but I didn't can to calculate this. > 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. Do you have experimental results of SQLite performance on SSD? Best regards. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
