Thank you kindly for all your suggestions!
>If you want SQLite to support all ACID properties you cannot change
>anything to speed up updates.
Making sure that I do not loose a character was my primary objective.
> If you are doing bulk updates, and are in a position to re-run the
> data in case of an error, wrap batches of 100 or more in a transaction.
> Just be sure to handle any error case that trips an automatic rollback.
>Make all your updates within a single transaction.
I will try to do something to that extent using timer and character counter.
I hoped that I could update the text stored in the database character by
character as fast as they
come from the keyboard driver. Unfortunately updates noticeably slow down the
display of typed characters.
>As a test, have you tried wrapping your updates in a transaction?
> That would isolate if the slow down is the actual writing of the data to
>disk.
It appears that single transaction is slow and I have to
make less transaction with more data.
>Where is the file sitting: A local drive, or something across a network
>connection?
File is sitting on a local drive. It is IDE Seagate 120MB drive – ST3120026A
Capacity: 120.9 GB
Speed: 7200 rpm
Average Read Time:8.5 ms
Cylinders:1023
Heads:256
Sectors: 63
· I/O data transfer rate - up to 100 Mbps
· Sustained data transfer rate - Up to 58 Mbps
· Average seek time - 8.5ms
· Average latency - 4.16ms
From this data nothing justifies the 120ms update of the record!
Thank you again.
Regards,
Samuel
__________________________________________________________________
The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo!
Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
