1. Serialize as json/xml and write to a new file each time, read latest file on start-up. Do no use DB for this. 2. Why not keep all in memory (50Mb-100Mb) and do the aggregation calculation on the fly? Do not use a DB for this.
mandag den 15. april 2019 kl. 14.47.30 UTC+2 skrev Gopalakrishnan Subramani: > > Dear All, > > I am reading positive about H2 for Raspberry PI, we are building a Linux > gateways, most of them run in small foot print Linux about 1 GB RAM to 4 GB > RAM, with 1 core to 4 core CPUs, heavily uses SD Card, rarely with emmc > storages. > > 1. Do you recommend H2 with Raspberry PI with SD card, where as we do 100+ > inserts every seconds, we can batch them into single build insert, query > 10000+ records every second for aggregation, count/min/max etc, delete 100+ > records every 5 seconds?, So given any time, the total size of the data in > the database may not exceed 1 million records, each record may be size of > 20 -50 bytes. > > 2. we have two types of data, > > 1. Configuration: First DB is for config files and we want to store > into H2 Database in separate file. This file is very rarely queried, very > few insert once in a month or so. > 2. Process Data: Second DB is for live data which we read from > sensors, we do 100+ inserts every seconds, query 10000+ records every > second for aggregation, count/min/max. > > Do you recommend to use 2 database files in H2 as Embedded mode, what is > the memory overhead/CPU overhead on the same? > > We are OK to loose the process data, the loss is about 15 mins data, where > as not OK to loose Configuration data. > > Regards, > > GK > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
