InfluxDB 1.1: 60% performance increase and new query functionality
1–10 of 49 posts
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#2Very good to hear that. Started to try influxdb as my tsdb for iot and looks very promising.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#3Currently using internally for production level work. They need to spend serious time making it easier to diagnose issues when they happen.
The log is simply not verbose enough and when I hit issues with telegram, kapacitor and influxdb I have to open up a github issue having no idea what is causing the issue.
Still highly recommended they just need to spend time making it easier to identify common problems. It'll help reduce the number of github issues they have opened too.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#4I'm looking forward to trying it out. I used it at home to build a live weather site for my backyard weather station: https://mhkweather.com
The performance went way down when I moved my DB from a ext4 SSD volume to a four-disk ZFS magnetic volume. I expected some slowdown but not as much as I saw. Looking forward to trying 1.1 to see if it improves things.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#5Nice work by the InfluxDB team.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#6Sweet. I had some 'getting oomkilled' problems with boundless queries back when I started using Influx for production early in the year, but it has been rock solid and performant since the later 0.1x releases.
> Support for regular expressions on field keys in the SELECT clause. For example, SELECT /cpu_\d/ FROM cpu
Woohoo! Very nice for making Grafana dashboards.
> The admin UI (port 8083) is now officially deprecated and disabled in this release
Ahh. I must be the only one using it, it gave kind of a good overview of all your collections. A bit of a pain to do from Grafana but oh well.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#7Sweet. I had some 'getting oomkilled' problems with boundless queries back when I started using Influx for production early in the year, but it has been rock solid and performant since the later 0.1x releases. > Support for regular expressions on field keys in the SELECT clause. For example, SELECT /cpu_\d/ FROM cpu Woohoo! Very nice for making Grafana dashboards. > The admin UI (port 8083) is now officially deprecat…
The admin UI was really good and they started to strip features away from it one by one and now it is disabled. It even could do simple graphs and was very useful for debugging.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#8Tried using in production, failed really badly performance-wise (granted, it wasn't a good fit - cardinality was high). Replaced with PostgreSQL and I'm seeing 2+ orders of magnitude improvement on c4.large vs r4.8xlarge before..
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#9Sweet. I had some 'getting oomkilled' problems with boundless queries back when I started using Influx for production early in the year, but it has been rock solid and performant since the later 0.1x releases. > Support for regular expressions on field keys in the SELECT clause. For example, SELECT /cpu_\d/ FROM cpu Woohoo! Very nice for making Grafana dashboards. > The admin UI (port 8083) is now officially deprecat…
The admin UI was really good and they started to strip features away from it one by one and now it is disabled. It even could do simple graphs and was very useful for debugging.
That seems to be their uncommunicated plan - to attract users to open source version and then remove features to offer just with enterprise product. They have done it with clustering support where after attracting people with promises they then removed it from open source version. Grafana as a replacement? It really does different things.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#10Can anyone verify the claims on their production setup? I'm always a bit weary of these announcements. It's easier to get big numbers like that on benchmarks than in real usage scenarios, has usually been my experience.