>
>
>I'm in the process of architecting the software for an embedded Linux system
>> that functions as a remote and local user interface to a control system.
>> There
>> will be a lot of analog (fast) data arriving via SPI bus and I'm thinking of
>> using SQLite to store this data in a well organized and easy to access
>> manner.
>> 
>> My main concern is performance. Has anyone had any similar application
>> experience they could comment on? I want to be able to insert data arriving
>> on the SPI bus and then query the data to update a GUI at a very high rate
>> (less than 250Ms). This is not real time so 250Ms is desirable but does not
>> have to be guaranteed.
>> 
>> Any thoughts or experience would be appreciated...
>  
>


>> We'd need more details for definitive answers, such as whether you're
>> using disk or FLASH based storage, your data and schema format.

>> Some things to consider:
>> - Batch inserts. Given your 250ms update requirement, you could perhaps
>>   batch data 4 times a second. That'll give you a very high insert rate.
>> - If using disk based storage, using ext3 with "data=journal" mount option
>>  The journal can be written and sync'ed very quickly.
>> - Experiment with indexing. Indexes will slow insertions, but improve
>>  querying.
>> - If the above is still too slow, and you're happy risking the database in
>>   the event of a system crash, then you can turn off synchronous updates.


Thanks for your reply.

I'm still in the planning stage so I don't have too many details. I'm working
on a test database right now that should answer most of my questions. I can play
with that as far as optimization if it's not fast enough. Batched inserts is a 
good idea though. Give the system a little more recovery time between inserts.

I will be on a flash file system though and that's totally new to me with a DB.
I've worked with big DB's on big hardware but never anything like this. I'm 
fairly
new to embedded work. SQLite just seem to be a good fit for this application. 
Lots
of data that needs to be stored and queried and various different ways. The last
time my company designed an application like this they invented their own DB and
it was (is) a disaster. I've already got it compiled and installed on my 
platform 
and I've been working with some embedded SQL (C) today. It's pretty easy to use 
considering how little it is. Never seen anything quit like it. Very impressive.



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

Reply via email to