On Thu, 2 May 2013 16:58:01 +0200
"Jan Slodicka" wrote:
> Hi Dan
>
> > What are your settings for pragmas "cache_size", "journal_mode" and
> > "synchronous"?
>
> cache_size/synchronous - default values
>
> Don't remember, which journal_mode was used for testing. Should be
>
Hi Dan
> What are your settings for pragmas "cache_size", "journal_mode" and
> "synchronous"?
cache_size/synchronous - default values
Don't remember, which journal_mode was used for testing. Should be WAL, but I
might have been lazy to write needed code.
The source code was meanwhile
On 2 May 2013, at 2:57pm, Jan Slodicka wrote:
> LIKE is used at the moment, but it has its perf limits as well. To prove it,
> here is a desktop benchmark:
>
> Desktop: W7, x64, Intel i5, 2.4 GHz
> 116 MB email table containing 1 html-formatted emails.
> SELECT ...
On Thu, 2 May 2013 11:16:06 +0200
"Jan Slodicka" wrote:
> I was testing various ways how to interrupt rebuilding of an FTS
> index. Ability to abort is vital as the app is running on a
> smartphone and has to meet responsivity requirements.
>
> Here is what SQLite offers
Hi Simon.
> I have much love for FTS but it chews up storage space, processing power,
and therefore battery life, something fierce. You may end up with a working
app but your users will find it reduces their battery life to an hour.
Sounds unbelievable. Can you bring some example, please?
In
On 2 May 2013, at 10:16am, "Jan Slodicka" wrote:
> I was testing various ways how to interrupt rebuilding of an FTS index.
> Ability to abort is vital as the app is running on a smartphone and has to
> meet responsivity requirements.
Sorry, I don't know an answer to your
I was testing various ways how to interrupt rebuilding of an FTS index.
Ability to abort is vital as the app is running on a smartphone and has to
meet responsivity requirements.
Here is what SQLite offers (AFAIK):
- Progress handler (with low nOps value): Relatively good with only
occasional
7 matches
Mail list logo