armon

9 ms·

61.
by armon 13y ago
This might be a little unclear, but if you check the documentation for agent configuration ( http://www.serfdom.io/docs/agent/options.html ), there is an option to provide a role. The role is the metadata support cu
62.
HyperLogLogs at work: easily estimating set cardinality(github.com)
3 points by armon 13y ago|0 comments
63.
Open sourced: A C implementation of Adaptive Radix Trees(github.com)
1 points by armon 13y ago|0 comments
64.
CUDA implementation of HyperLogLog's for cardinality estimation(github.com)
4 points by armon 14y ago|0 comments
65.
by armon 14y ago
I'm guessing the authors deployed to production with no indexes on their collections. This means the cost of most queries was probably O(n). This could go unnoticed in development where N is small, but is unacceptable once you have any real
66.
by armon 14y ago
It is actually just a difference of naming. Gauges in statsd operate the same as kv data in statsite. Originally, both projects referred to them as kv, this seems to be a more recent change in statsd.
67.
by armon 14y ago
I work at Kiip, where we write primarily in Python, Erlang and C. We have built several in-house analytics systems than can handle upwards of 300K qps. We are hiring too: http://kiip.me/jobs
68.
by armon 15y ago
I work at Kiip, and I can confirm that our "non-durable purely in-memory solution" is Redis.
69.
by armon 15y ago
I'm not saying that one solution avoids the need for setting up things in a sane way. In both cases, you need to configure things properly or you can shoot yourself in the foot. However, depending on the systems your company uses and your c
70.
by armon 15y ago
I think if you take a moment to read the context you would have a better understanding of the security issues involved. EC2 acts like one giant multi-tenant network. The only thing preventing access to your nodes is the SG policies, which a