Did you run your test using ReadFile?
Brandon, Nicholas (UK) wrote:
I just tried (hadn't noticed that option before) to go from
2000 to 4000 and 8000, without noticing any difference. I
might try next week to raise the page size to 50k and see if
it makes a difference?
On the
Hello Julien,
JR>
JR> I can give you a few timings I have to give you an idea:
JR>
JR> Initialisation: connects to DB, pro-compile some queries, load
JR> structured data (SELECT * FROM Objects; i.e. sequentially, no blobs)
JR> Load Blobs: load 1/4 of all Blobs (each ~23k of size, I just
>
> I just tried (hadn't noticed that option before) to go from
> 2000 to 4000 and 8000, without noticing any difference. I
> might try next week to raise the page size to 50k and see if
> it makes a difference?
>
On the presumption the Sqlite allocates new pages on the page boundary I
> > One more thing, did raising the limit on the number of pages SQLITE
> > can cache internally have any effect?
>
> I just tried (hadn't noticed that option before) to go from 2000 to 4000
> and 8000, without noticing any difference. I might try next week to
> raise the page size to 50k and see
Mark Spiegel wrote:
> [...]
Thanks for the explanation. Yes, I'll have to make sure not to use this
technique when the file is too large. But I think there is definitively
an improvement for us to pull data in cache whenever possible.
> Given that you can't write your own VFS, there is
5 matches
Mail list logo
