I read that. The Mozilla people point out that their advantage was with
a large volume of small transactions. They benefit from not destroying
the cache between transactions and by conserving memory with large
numbers of users. They point out that relaxing the ACID requirements
also aids throughput and when you think about it is actually necessary
to get large gains from the persistent cache.
If the ratio of reads to writes is great the ACID capability should not
impact performance much. Our AJAX has reads outnumbering writes and may
benefit from an approach like test_server.c.
Joe Wilson wrote:
Shared cache mode would be better named "persistent cache mode" because
its main effect is to permit one thread to not flush the cache after
each transaction. The people at Mozilla report that they use it and get
better throughput on small transactions.
You've probably read this. It's useful information for any performance
minded developer using SQLite:
http://developer.mozilla.org/en/docs/Storage:Performance
Mozilla no doubt benefits from a shared cache, but its transaction throughput
improvement is largely due to deferring all database write operations to a
background thread, making the foreground database writes seem instantaneous.
However, this lazy writing drops Durability in ACID. This is described in the
above link.
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545433
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
