I found few topics on this issue but still. For instance from here http://www.mail-archive.com/sqlite-users@sqlite.org/msg54904.html. I have similar problem of writing multiple small data (max 100bytes per entry), but do not think that those advices from upper link were right. I have to tell that I have no idea how SQLite of Flash file system is implemented but lets pretend that there is no FFS and SQLite and storage is implemented using hand crafted drivers optimised for writing as many times as possible (endurance).
in case of for http://download.micron.com/pdf/datasheets/flash/nand/2gb_nand_m29b.pdf (that is just first link from my search engine) there are 2048 blocks for 2Gb (256 MB) device and each block has 64 pages and device endurance is 100k erasures. That men that in ideal world I am able to write at least NumberOfWriteUnits * Endurance = 64*2048*100k = 1.0e+10 times. In 10 years that mean 40 writes per second. Of course I do not have that may space but I can download data frequently enough and make space for new data. Lets say that memory utilisation is not that efficient and we have overhead by factor 100 per write using SQLite, Flash file system and having some other data on flash and other unexpected issues. This still means that we end up whit at worst 1 write per 2 seconds over 10 years what is I think enough for most this kind of applications. Am I right? Are there more and less efficient file systems for this task? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
