3 ms·
Can someone tell me why someone would want to write a database in Go/Python/...? Or is Go just a wrapper in this case? I am looking to store small time series
by raindrop777 12y ago
Can someone tell me why someone would want to write a database in Go/Python/...? Or is Go just a wrapper in this case?
I am looking to store small time series data (only 100 points), but millions of them. I currently use sqlite. Any other suggestions that I could use?
- bduerst 12y agoIt's all dependent on what you're trying to do. Sqllite is surprisingly robust for simple things. Are you experiencing any issues yet, and what kind? What's the transactional activity with that time series you're storing? (i.e. are you writing these individually each millisecond or are you writing in batches every hour)
- rcarmo 12y agoRRDTool?
- atmosx 12y agoI'd go with PostgreSQL, takes 30-35 MB of RAM for one running connection. The entire stack (db + httpd + ruby/python/php) should take less than 150 MB. You have another ~ 300 in the prior model B. Go should be faster and more efficient than python/ruby so I'd expect even less RAM/better performance. SQLite3 these days is good for embedded devices but that's about it IMHO.
- ethbro 12y agoI suppose for the same argument that can be made for single-language-but-inefficient configuration systems. When you're doing a basic process, reliability >> efficiency. And sometimes more pieces in your stack just decrease reliability of the entire system. (Admittedly! Rolling your own version of an already well-implemented stack component is not without its peril as well)
- jrv 12y agoMillions of time series with a small number of points each actually works very well with Prometheus.