TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

InfluxDB Clustering Beta and Data Explorer

64 点作者 pauldix将近 9 年前

4 条评论

perlin将近 9 年前
We evaluated InfluxDB for our TSDB solution and found it to be generally high performance (up to about 100k unique series). Kapacitor also had some promising features for realtime aggregations, but was ultimately pretty buggy and didn&#x27;t have support for out-of-order event processing. All in all, it looks like a great suite of products and we&#x27;re curious to see how it evolves over the next few years.<p>Like many other users here, we were disappointed about paid clustering, but when the original press release said $400, we were willing to wait it out and see. However, we ultimately decided to go a different direction after seeing they wanted $20k+ to run clustering on a 256GB node. We ingest 10s of millions of data points per day from IoT sensors, and expect our data size to far exceed that capacity.<p>That said, we plan to run our own Cassandra cluster w&#x2F; KairosDB (<a href="http:&#x2F;&#x2F;kairosdb.github.io&#x2F;" rel="nofollow">http:&#x2F;&#x2F;kairosdb.github.io&#x2F;</a>) acting as a read &#x2F; write abstraction layer. It&#x27;ll cost us about $11k to run the cluster for the year, with 3 nodes @300GB&#x2F;ea., leveraging Cassandra&#x27;s (free) and open source clustering, HA, and replication technology.
评论 #11964291 未加载
linsomniac将近 9 年前
I have just shut down 95% of my collectd&#x2F;graphite infrastructure after migrating it over to InfluxDB+telegraf+grafana. I&#x27;m loving it! Since shutting down collectd, system load and io wait time across my fleet has gone way down, and available CPU has gone way up.<p>Though I wouldn&#x27;t say it was a smooth transition. I started with 0.8, IIRC, and while it worked ok it used an amazing amount of storage. 4GB for a year worth of graphite data blew up to 100GB for a month of InfluxDB.<p>I gave up on InfluxDB a few times during the process, but at 0.11 I tried it again and is has been pretty good. We are only putting the Telegraf data and one small service statistic in it, but the storage is pretty reasonable at 12GB for a few months of data. Querying and graphing the data with Grafana is great.<p>If you have tried it before 0.11, definitely try it again. The guys giving a Prometheus talk at PyCon were really down on InfluxDB, but they hadn&#x27;t tried it for 6 months. I was like &quot;Yeah, it was unusable then&quot;. I wanted to like Prometheus, but I just couldn&#x27;t figure out how to feed my data into it.
评论 #11964901 未加载
zenlot将近 9 年前
Great news from influxdata. Though all of these features (clustering, monitoring, and data elxploration) could be released with standard edition. The start of InfluxDB looked very promising, not sure if people feel the same with the chosen marketing model.
评论 #11963269 未加载
评论 #11963041 未加载
评论 #11962931 未加载
mattbillenstein将近 9 年前
I really like the influxdb interface -- reading and writing data are super simple, but in some recent testing I did, it really really hated high-cardinality data sets.<p><a href="https:&#x2F;&#x2F;docs.influxdata.com&#x2F;influxdb&#x2F;v0.10&#x2F;guides&#x2F;hardware_sizing&#x2F;#when-do-i-need-more-ram" rel="nofollow">https:&#x2F;&#x2F;docs.influxdata.com&#x2F;influxdb&#x2F;v0.10&#x2F;guides&#x2F;hardware_s...</a><p>Show stopper if you&#x27;re in the same boat that I am.
评论 #11963326 未加载