Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
NOSQL
Home
+ new post
About this group
Join this group
Message from discussion Which database is most appropriate for sensor logging
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
K.S. Bhaskar  
View profile  
 More options Mar 25 2011, 1:41 pm
From: "K.S. Bhaskar" <ksbhas...@gmail.com>
Date: Fri, 25 Mar 2011 10:41:19 -0700 (PDT)
Local: Fri, Mar 25 2011 1:41 pm
Subject: Re: Which database is most appropriate for sensor logging
Print | View thread | Show original | Report this message | Find messages by this author
How does the application code read the sensors?  For example, is there
a process for each sensor that hangs for a second and reads an IP
address?  Are there multiple processes each of which polls a group of
sensors?  Is there a device driver that reads the sensor data and
asynchronously e.g., via DMA, and puts the readings in a shared memory
segment?

What are the requirements for availability?  Recoverability in the
event of hardware failure?

Sounds like a nice little afternoon project with GT.M (http://fis-
gtm.com).  Full disclosure: I manage GT.M.

Regards
-- Bhaskar (yes, it's my last name, but that's what I'm called)
ks dot bhaskar at fisglobal dot com <-- send e-mail here

--
GT.M - Rock solid. Lightning fast. Secure. No compromises.

On Mar 24, 6:27 am, Heiner Bunjes <h.bun...@googlemail.com> wrote:

> Hello!

> I need a database to log and retrieve sensor data.

> The scale is as follows:

> (01) Tenthousand sensors deliver 1 record per second each
>      -> Insert rate = 10kilorecord/s
>      -> Insert rate = 315 gigarecord per Year

> (02) They have to be stored for ~3 years
>      -> Size of database = 1 terarecord

> (03) Each record has about 200 bytes
>      -> Size of database = 200TB

> (04) The system will start with just 700 sensors but will
>      soon increase upto the described volume

> The main operations on the data are

> (05) Append the new records to the database
>      (written records are never changed)

> (06) Return all records for sensor X with a timestamp
>      between timestamp_a and timestamp_b

> (07) Return the records specified in (06) ordered by
>      timestamp

> (08) Delete all records older than Y

> Further the following is true

> (09) The database system MUST be free and open source

> (10) The DB SHOULD be easy to administrate

> Which is the most appropriate database for this?

> p.s.:
> I am currently havin a look at riak but I'm not sure how
> to efficiently implement (06) and (07) or if there is a
> much better choice than riak.

> Thanks
> Heiner


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google