jerry scharf wrote:
I would not use RRD or anything like that to handle the data directly.
At a dollar per GB, why not keep all the sensor data forever? Then use
alarm tools, RRD and the like working against the data store. You
never know what question you might want to ask tomorrow, and without
raw data you lose that ability. All you need to capture is the sensor
id, type, value and sample time. Given the research flavor of the
site, this seems quite reasonable.
I'd second that. I've been collecting the raw data for DIY Zoning
project since 2001 (up to 10 sensors) - and the trace file is barely
over 10M in size.
On the other hand, RRD and suchlike are handy for keeping statistics,
data visualization etc. So I'd suggest storing the data both in the raw
trace and RRD - the overhead is minimal.
Oh, and when you store the raw data, make sure that it is in a
grep(1)pable and cut(1)table format - helps a lot.
Jerry Scharf
--vt
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
