21–30 of 79 posts
This looks like the exact feature-set we need at my company; we're in the middle of moving to Redshift but I'll be keeping an eye on Influx. I know it's early days but I didn't see any information about cluster management - how does one setup an Influx cluster, can it be resized, what kind of hardware does it prefer?
Earlier quoted context omitted.
This project looks really, really promising, thanks for working on it! How robust/scalable in your opinion the backend is at this stage? I'm just trying to set my expectations properly when checking it out. Thanks, Sasha
We're writing the clustered portion of it right now. That won't be available until December, but we'll have performance benchmarks on a variety of configurations. The single node performance at this point for writes is tens of thousands of points per second if batched, and for reads we haven't optimized yet. Queries that only have to go through a few hundred thousand points should return in For now we're focused on c…
sounds interesting; i am currently using hbase for similar purposes. Do "tables" have to be created explicitly, or can I just store a value into a timeseries, and if the ts doesn't exist yet it will be created?
You can just write data in on the fly. Time series get created when you write the first point. You also can create new columns on the fly. And there's no enforcement of a data type across all values for a given column. That's on the user.
https://github.com/lsh123/stats-rrdb
An important part for me was the desire to completely separate data and UX (so no graphite). Added bonus is ability to control resources (e.g. memory/disk usage).
We run it in production for quite some time processing hundreds of data updates per second and tens of queries per minute.
Earlier quoted context omitted.
You can just write data in on the fly. Time series get created when you write the first point. You also can create new columns on the fly. And there's no enforcement of a data type across all values for a given column. That's on the user.
Great. I am looking at integrating it into my fork of ethercalc so i can store not just the metrics but also some of the indicators and statistics i compute on them. For my use cases (R and spreadsheets) it would be handy if i could get results in csv format straight from the API when i make a query.
The sandbox appears to be down, but I'm a little concerned about the security. Can database users be created that only have read access?
However, security is probably not something to bother with in sandbox since it's not HTTPS. We're looking at it now, and should have it back up in a bit.
I was actually looking at a bunch of open source time series databases and settled on kairosdb but this looks pretty nice. I think there is a hackernews rule someplace that a more interesting tech alternative shows up right when you decided to go with something else. For reference here is the list I created when researching these: http://opentsdb.net/overview.html Built on HBASE http://www.gocircuit.org/vena.html Bui…
I'm one of the committers. The project is still early stage. At this point we're looking for feedback on the API, which we're planning on finalizing this month. Would love to hear about anything you'd like changed or added to the API.
I wouldn't use this bastardized SQL dialect. SQL comes from relational databases, which comes from relational algebra, which is an exceptionally poor model for time series data. It's going to end up a mess and confuse people. SQL is already a mess by itself. I would simply use functions and operators over time series or data frame types. Perhaps take a look at the R zoo library for examples of more advanced things pe…
It appears to be built with Go. https://github.com/influxdb/influxdb
It's definitely built with Go.