High-frequency time series database

AI Thread Summary
When choosing a database for high-frequency time series data, the discussion highlights three options: MongoDB, Kyoto Cabinet, and HDF5. The user plans to insert 1,200 rows with 8 entries per second, estimating around 5 GB of data daily. HDF5 is noted as a storage scheme rather than a traditional database, lacking a server for query processing. In contrast, MongoDB is a full-fledged database requiring a server, while Kyoto Cabinet is also described as a storage scheme. The emphasis is on speed, suggesting that for high-frequency data, a storage scheme like HDF5 or Kyoto Cabinet may be preferable. HDF5 is recognized for its versatility and popularity in scientific and engineering fields, while Kyoto Cabinet's appeal and performance are questioned. Overall, the discussion leans towards considering HDF5 or Kyoto Cabinet for optimal speed in handling time series data.
meanrev
Messages
116
Reaction score
2
I'm choosing a database to write high-frequency time series data onto and have narrowed it down to MongoDB, Kyoto Cabinet or HDF5.

I will be inserting 1200 rows of 8 entries per second, cumulating about 5 GB of data per day I'm estimating.

Does anyone have experience between the three and could facilitate me in making the decision?

Thanks!
 
Technology news on Phys.org
Well, I don't know much about databases; but I will give one silly opinion...

The thing is I have been trying to learn various things available within Python...one of those things I run into was, precisely, HDF5. When I read about HDF5, I understood that it was a storage scheme and not necessarily a database (i.e., there is no database server running with its own intelligence to answer queries or return sets or anything like that).

Of the other two choices that you mention, I just quickly read the main webpages and it looks like MonoDB is a real database (requires a server) and Kyoto Cabinet does not, this last, again, it's just a storage scheme.

So, my first opinion, if you need speed, is to forget about using a real database and stick to a storage scheme...so, Kyoto or HDF5.

It seems Kyoto talks about one key,value per line...does not seem too impressive as a storage scheme...but maybe that's where speed comes from.

HDF5, from what I remember, is actually rather versatile as far as as to what it can store.

The Kyoto site does not look like much...how popular is this?

Just becauss I learned about HDF5 before I ever heard about Kyoto, it sounds like HDF5 is more popular within the scientific/engineering community...

Anyway, that's my un-educated opinion.

gsal
 
Dear Peeps I have posted a few questions about programing on this sectio of the PF forum. I want to ask you veterans how you folks learn program in assembly and about computer architecture for the x86 family. In addition to finish learning C, I am also reading the book From bits to Gates to C and Beyond. In the book, it uses the mini LC3 assembly language. I also have books on assembly programming and computer architecture. The few famous ones i have are Computer Organization and...
I have a quick questions. I am going through a book on C programming on my own. Afterwards, I plan to go through something call data structures and algorithms on my own also in C. I also need to learn C++, Matlab and for personal interest Haskell. For the two topic of data structures and algorithms, I understand there are standard ones across all programming languages. After learning it through C, what would be the biggest issue when trying to implement the same data...
Back
Top