pauldix

34 ms·

301.
by pauldix 11y ago
You're right, there are plenty of examples where that didn't happen. However, I've seen enough examples where it has. Enough that I think it's a bad idea to do side projects while you have full time employment. Unless th
302.
by pauldix 11y ago
The primary point of my post was that the law doesn't actually matter in practice. Regardless of if your points 1 and 2 are demonstrably false (thus the person is protected by 2870), someone trying to commercialize a side project (or a
303.
by pauldix 11y ago
Despite the fact that California has this law, it doesn't matter in a practical sense. A scenario I've seen play out multiple times: 1. Employee creates side project 2. Employee quits to pursue side project as a company 3. Former
304.
The InfluxDB SHOW STATS Query(influxdb.com)
8 points by pauldix 11y ago|0 comments
305.
by pauldix 11y ago
The negative is that time is a finite and limited resource. If a junior person spends their time learning about Fortran or some other esoteric thing while their peers learn skills or languages that are in demand, the junior person that lear
306.
InfluxDB 0.9.3 out with compression, improved write throughput and 0.8 migration(influxdb.com)
18 points by pauldix 11y ago|1 comments
307.
Will machines eventually take on every job?(bbc.com)
1 points by pauldix 11y ago|0 comments
308.
by pauldix 11y ago
InfluxDB CEO here. I've already forwarded to our lawyers to ask. Reading through the patent there are some key differences between what they describe and what we built.
309.
Announcing Chronograf, a visualization tool for InfluxDB(influxdb.com)
6 points by pauldix 11y ago|0 comments
310.
by pauldix 11y ago
Sure, will have a look tomorrow morning first thing
311.
by pauldix 11y ago
Our goal is to release a point release in the 0.9 line every 3 weeks for the next 3-5 months. Once we've reached a good level of stability and implemented some of the key features on our roadmap, we'll start the 1.0 release cycle.
312.
by pauldix 11y ago
I haven't really formulated an opinion on pull vs. push models for metrics. For us, we're aiming to be more than just a DevOps platform. Those kinds of metrics are just one of the use cases we're trying to hit, which means th
313.
by pauldix 11y ago
DataDog is more of a fully featured application. We want to be a platform for people building custom monitoring, DevOps, and sensor data applications for their needs. As for cAdvisor, my hope is that it gets updated to work with the new Inf
314.
by pauldix 11y ago
We'll have to fix the issues of installing on two systems. For the issue linked to InfluxDB I assume it was for the client tags. The tagging issue in Telegraf was actually a problem with the InfluxDB client. Anyway, we're committe
315.
by pauldix 11y ago
Yeah, had to speak at another conference. Going to block it off for next year though!
316.
by pauldix 11y ago
InfluxDB CEO here. Happy to answer questions about InfluxDB or Telegraf
317.
InfluxDB 0.9.1 and Telegraf 0.1.2 released(influxdb.com)
30 points by pauldix 11y ago|16 comments
318.
Monitoring a Docker Cluster with Telegraf and InfluxDB(benbailey.me)
4 points by pauldix 11y ago|0 comments
319.
by pauldix 11y ago
Yep, compression work is starting in the 0.9.2 release cycle. We'll be testing out those compression methods along with other stuff like delta encoding
320.
by pauldix 11y ago
On the performance problem, my guess is that you wrote in a bunch of columns and had those in where clauses. I hope the documentation made it clear that you'd be range scanning over data and that you probably wouldn't get desirabl
321.
by pauldix 11y ago
InfluxDB CEO here. Those problems with corrupting data were with the 0.8 line of releases. But to be honest there are people that have been running that and 0.7 in production for almost a year without problems. Your mileage may vary, but we
322.
Announcing Telegraf, a metrics collector for InfluxDB(influxdb.com)
39 points by pauldix 11y ago|5 comments
323.
by pauldix 11y ago
yep, should be getting updated in the next day or so. We're on it ;)
324.
by pauldix 11y ago
There isn't a limitation on the number of tags per data point. Although I assume at some point it'll become a performance bottleneck. The limitation you're thinking of is the number of fields. Currently, you can only have up
325.
by pauldix 11y ago
Sorry to ruin a perfectly good excuse :) Lies, damn lies, and delivery estimates
326.
by pauldix 11y ago
We'll update the readme. Overlooked in the push to release. The docs on InfluxDB.com should be accurate
327.
by pauldix 11y ago
We will be starting work on a new storage engine or an optimized version of what we have now that will add compression. Tentatively, that will start in the 0.9.3 release cycle. First rule of software: make it work, then make it efficient
328.
by pauldix 11y ago
Have a recommendation for what we should be doing? More than happy to update how we package to make things easier or more idiomatic
329.
by pauldix 11y ago
We will be doing that testing in the future. I've already talked to Kyle about our design. We'll iterate on his and other smart people's feedback. That's one of the reasons the clustering alpha right now :)
330.
by pauldix 11y ago
looking at it, should be fixed in a few minutes

More ›