postwait

5 ms·

1.
by postwait 3y ago
on-premises.... premises... not premise
2.
by postwait 7y ago
I am fairly certain this is the fastest method available https://sorting.cr.yp.to/index.html
3.
by postwait 8y ago
I think this misrepresents the pull vs. push issue. I wrote something up two years about this that was pretty well received. https://www.circonus.com/2016/06/pully-mcpushface/
4.
by postwait 8y ago
IRONdb ( https://www.irondb.io/ ) Can house multi-tenant-safe prometheus long-tail storage as well as others (graphite, opentsdb, influx, etc.). Put it all in one place, scale it up, radically storage efficient and has stron
5.
by postwait 8y ago
In addition, if you are a freelancer in the US you have access to group healthcare.
6.
by postwait 8y ago
Most universities have special access to both IEEE and ACM publications (as well as many others). They pay for this access.
7.
by postwait 8y ago
I am an IEEE member. I am not sure why anymore, mostly I think it is important to support the industry. I am also an ACM member and I find that very valuable. The community is good, the policy engagement is good, the publications are exce
8.
by postwait 8y ago
We have customers that generate tens of millions of measurements per second. Lots of low-level systems latencies can be collected at high volume. Also, high volume online services can easily generate this order of magnitude.
9.
by postwait 8y ago
I find this discussion fascinating. When I hear people advocate for SLOs (and SLIs) they are often quite rigorous in how they approach it... that is until the very last step where they hand-wave the math and produce numbers that don't
10.
by postwait 9y ago
Reducing "Other TSDBs" to log-structured-merge trees is misleading. Any large-scale TSDB has something sophisticated underneath and LSM is often just one tiny part of that. I would argue (as most do) that any TSDB "simply u
11.
by postwait 9y ago
Try IRONdb... Relatively fast restarts, linear cluster scalability and no downtime when a single node is malfunctioning.
12.
by postwait 9y ago
Storing and retrieving data has never been all that hard. The challenge is having user-interactive performance on complex queries against the data. Comparing and correlating and deriving and integrating and ... (lots of other analysis).
13.
by postwait 9y ago
Relentless change is most likely the motivator for these innovations. However, I don't think it is needless innovation or innovation for the same of innovation. Personal opinion that there isn't much innovation in what this arti
14.
by postwait 9y ago
Find a group of fellow founders that you can talk with. Even if it is just one or two. As a founder, I can relate to the stress and suffering. Sharing can make all the difference.
15.
by postwait 10y ago
High school teacher.
16.
by postwait 10y ago
Ummm https://github.com/keithf4/pg_partman has been around for a long time and is used all around the world... AND it doesn't require cron jobs. Much tighter solution
17.
by postwait 10y ago
A more thorough investigation of pull vs. push. https://www.circonus.com/pully-mcpushface/
18.
by postwait 10y ago
If you care about correctness of data, solid data retention and good analytics (prediction, forecasting, etc.) then you should take a look at Circonus. http://www.circonus.com/ 500 metrics accounts are free for life. Built
19.
by postwait 11y ago
We use it every day at Circonus. One of us is learning something new about how our stuff works every single day.
20.
Entrepreneur ProTips (from a bootstrapper)(lethargy.org)
3 points by postwait 12y ago|0 comments
21.
by postwait 12y ago
Oh, yes. Like all the code I've contributed with no reciprocation demanded.
22.
Beware of strace(lethargy.org)
4 points by postwait 13y ago|0 comments
23.
Understanding Data with Histograms(circonus.com)
2 points by postwait 14y ago|0 comments
24.
by postwait 14y ago
"Talks should always be reactionary rather than anticipatory: they’re going to come off as more natural, more interesting, and above all, more valuable." I think that's not true at all. There is room for both. I would say do not mix them.
25.
What's in a number? [analytics](circonus.com)
1 points by postwait 15y ago|0 comments
26.
by postwait 15y ago
Columbia, MD Circonus - https://circonus.com/about/careers Startup. Game on. careers@circonus.com
27.
by postwait 16y ago
Enjoying the discussion. The argument that HTTP status codes are "good enough" is one perspective. While I don't buy into everything in the "spec" proposed here, I think having application specific errors that make more sense is reasonabl
28.
#ywahusty: you will always have users smarter than you(lethargy.org)
1 points by postwait 16y ago|0 comments