I wanted to try it, but the downloads page presents a popup asking for your name and email address, and you cannot dismiss it. https://www.influxdata.com/downloads/
InfluxDB 1.1: 60% performance increase and new query functionality
41–49 of 49 posts
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#42I wanted to try it, but the downloads page presents a popup asking for your name and email address, and you cannot dismiss it. https://www.influxdata.com/downloads/
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#43I wanted to try it, but the downloads page presents a popup asking for your name and email address, and you cannot dismiss it. https://www.influxdata.com/downloads/
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#44I wanted to try it, but the downloads page presents a popup asking for your name and email address, and you cannot dismiss it. https://www.influxdata.com/downloads/
That should be getting changed to have a dismiss x on the upper right. TBH I thought it had been done already. Overly aggressive marketing department...
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#45I wanted to try it, but the downloads page presents a popup asking for your name and email address, and you cannot dismiss it. https://www.influxdata.com/downloads/
But honestly, if a person won't share contact information in exchange for the fruits of thousands of hours of someone's labor then they don't have much of a need for it and the creators probably aren't missing them.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#46I wanted to try it, but the downloads page presents a popup asking for your name and email address, and you cannot dismiss it. https://www.influxdata.com/downloads/
It's OK; their email validation is borked (just put in anything matching `\w@\w`, no domain necessary) and give something random for the name. Modals like that are pretty standard practice for enterprise mumbo jumbo; they only need to catch someone foolish enough to put in real data once to be worthwhile.
http://www.regular-expressions.info/email.html
> Don't go overboard in trying to eliminate invalid email addresses with your regular expression. The reason is that you don't really know whether an address is valid until you try to send an email to it. And even that might not be enough.
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#47I am wondering the choice of go as language to build a database. I am a big fan of golang for some workload but the GC will kill performance in a database, wouldn't? I am not being a brat I am seriously wondering how much GC affect the overall performance.
Here is our measurement dashboard for a functional test cluster: http://dash.etcd.io/dashboard/db/functional-tests?from=now-2...
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#48I am wondering the choice of go as language to build a database. I am a big fan of golang for some workload but the GC will kill performance in a database, wouldn't? I am not being a brat I am seriously wondering how much GC affect the overall performance.
> I am a big fan of golang for some workload but the GC will kill performance in a database, wouldn't? Cassandra and HSQLDB are written in Java for example which usually suffer from much larger GC collections/pauses (though you can read a book or two on the subject and tune it). So is Neo4j, a graph database. Or Datomic in Clojure (which runs on the JVM). Then there's Mnesia written in Erlang. A time series database,…
Re: InfluxDB 1.1: 60% performance increase and new query functionality
#49Sweet. 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…
Before we actually remove the admin interface, we'll have a modern version of it in the now OSS Chronograf. Basically moving that functionality to there so we can iterate on the UI separately from the DB.