SQLCipherSpeed: Another nice project you've put together. It's already
helped by localize my main performance issues. Whilst I find the
performance is still reasonable. With a little tactical de-normalizing
On May 5, 6:43 am, Stephen Lombardo <
sjlomba...@zetetic.net> wrote:
> Hi Mike,
>
> I'm glad to hear you resolved the crash issue, that was a puzzler. As far as
> the performance of a like operation, it's going to depend a lot on the
> specific query being run, whether or not its doing a full table scan, etc.
> Here are some guidelines.
>
> As a general rule, SQLCipher is almost as fast as standard SQLite for
> queries that use indexes because we are able to seek to and decrypt
> individual pages very quickly. Overhead for these types of queries can be as
> low as 5%.
>
> On the other hand queries that do a full scan effectively need to decrypt
> every page for that table, which is very expensive. You should probably
> expect a 50% overhead for SQLCipher in these cases. You can use SQLite's
> EXPLAIN and EXPLAIN QUERY PLAN functions to gain insight into the types of
> operations a query will involve (
http://www.sqlite.org/lang_explain.html).
>
> Given the size of your database, one immediate suggestion would be to use a
> full text index instead of LIKE queries.
>