Re: [sqlite] perfomance optimisations on tmpfs file system

2009-09-21 Thread Thompson, Nick (GE EntSol, Intelligent Platforms)
Ah, great "first post" :( and now I'm going to compound my crimes by
replying to self with a real subject heading - Sorry about that.
 
> Hi, (SQLite v3.6.17, on ARM with Linux 2.6.18)
> 
> I'm currently investigating the applicability of SQLite in an embedded
> application. Part of this would be to store configuration data, for
> which SQLite seems like a natural fit.
> 
> I also have a requirement for exchange of realtime data between
> processes. The data is only stored in RAM (probably on a tmpfs
> filesystem in Linux, so it can be shared) and, while atomic commits
are
> valuable, it is not important to be robust in the face of reboots.
> 
> Testing shows that I can commit writes at about 400 transactions per
> second and read tables at about 1400 queries per second. I have tried
> changing PRAGMA settings for journal_mode to OFF, synchronous OFF and
> temp_store to 2. These seem to have a small impact (to about 410
> commits/second).
> 
> PRAGMA journal_mode; gives no output though which makes me suspicious
as
> to whether it is doing anything.
> 
> The performance so far is perhaps adequate, but since it takes up
almost
> 100% CPU to do it, it will of course tail off when I start to do
> anything with the data.
> 
> Are there any other configuration options (per DB) that I should be
> considering, or other tips that might be relevant?
> 
> Thanks,
> Nick.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] (no subject)

2009-09-21 Thread Thompson, Nick (GE EntSol, Intelligent Platforms)

Hi, (SQLite v3.6.17, on ARM with Linux 2.6.18)

I'm currently investigating the applicability of SQLite in an embedded
application. Part of this would be to store configuration data, for
which SQLite seems like a natural fit.

I also have a requirement for exchange of realtime data between
processes. The data is only stored in RAM (probably on a tmpfs
filesystem in Linux, so it can be shared) and, while atomic commits are
valuable, it is not important to be robust in the face of reboots.

Testing shows that I can commit writes at about 400 transactions per
second and read tables at about 1400 queries per second. I have tried
changing PRAGMA settings for journal_mode to OFF, synchronous OFF and
temp_store to 2. These seem to have a small impact (to about 410
commits/second).

PRAGMA journal_mode; gives no output though which makes me suspicious as
to whether it is doing anything.

The performance so far is perhaps adequate, but since it takes up almost
100% CPU to do it, it will of course tail off when I start to do
anything with the data.

Are there any other configuration options (per DB) that I should be
considering, or other tips that might be relevant?

Thanks,
Nick.


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users