brian_cunnie

19 ms·

1. 181.▲
   by brian_cunnie 10y ago

   IIRC, there were two traits that don't seem to change over the course of one's life: gregariousness, and level of anxiety. Traits other than those two can change. Classic example: an alcoholic who becomes sober.
2. 182.▲
   by brian_cunnie 10y ago

   I just kicked in $250, one-time. To echo other posters, this was something I've been meaning to do.
3. 183.▲
   by brian_cunnie 10y ago

   I prefer the open plan — I love it! In my 30+ years of corporate life, I have the smallest working space ever (36 inches of desk space), and I think it's awesome. I work at a place that does pair programming, so I'm always engaged
4. 184.▲
   by brian_cunnie 10y ago

   [author] Digital Ocean is a great deal! Thanks for pointing that out. The reason I use {aws,azure,google} to host my NTP servers is that my day job is developing a VM orchestrator (BOSH) for Cloud Foundry, and BOSH doesn't support Digi
5. 185.▲
   by brian_cunnie 10y ago

   [author] Yeah, maybe that's why my AWS instance is the most jittery of my 4 timeservers (Google, Hetzner, Azure).
6. 186.▲
   by brian_cunnie 10y ago

   Here is a visual representation of the affect of the snapchat broken-ness on my NTP server: https://cloud.githubusercontent.com/assets/1020675/21468123/... Note that inbound traffic which was steady at ~4k pa
7. 187.▲
   by brian_cunnie 10y ago

   [author] My bad — I never wrapped it up. Thanks to the HN interest, I'll try to write Part 3 over the winter break. The short version is this: it's gonna cost a couple of hundred dollars to run a 1Gbe NTP server in pool.ntp.org, b
8. 188.▲
   by brian_cunnie 10y ago

   [author] NTP runs fairly decently in a VM. Don't take my word for it — look at the graphs of my servers: Here's my Google VM, notice the jitter is within +/- 5 milliseconds: http://www.pool.ntp.org/scores&#x2F
9. 189.▲
   by brian_cunnie 10y ago

   [author] Thanks, Spooky23. As you pointed out, contributing to the community takes more time than originally expected.
10. 190.▲
    by brian_cunnie 10y ago

    [author] My bad. Now that the post has been picked up on HN, I'll try to write up a conclusion.
11. 191.▲
    by brian_cunnie 10y ago

    [author] > I wish he'd explained somewhere how they leapt to examining virtualized NTP clients... I had a hunch [wrongly] that the traffic was caused by a particular operating system. I didn't have enough machines to run the te
12. 192.▲
    by brian_cunnie 11y ago

    The recommendation (swap == 2 x RAM) was more common in the nineties when RAM was much more expensive. It was a reflection that the resident set size (RSS) of a process is often a fraction of its Virtual Memory footprint (often an order of
13. 193.▲
    by brian_cunnie 11y ago

    Thanks mini. I'm not sure why they banned me (I used a link in my first post?), but they let me create another account, and am now using that one.
14. 194.▲
    by brian_cunnie 11y ago

    Dylan, that was our thinking exactly--the URL would look unbelievably fake.
15. 195.▲
    by brian_cunnie 11y ago

    I personally am very interested in IPv6, but the regular expression notation is more complex than IPv4: IPv4 has four decimals separated by dots; IPv6 has as many as 8 double-byte hex characters, sometimes as few as one (e.g. ::1). Plus, ot
16. 196.▲
    by brian_cunnie 11y ago

    You're absolutely correct--amount of swap isn't as good a metric as how much it's stressed (how much is being swapped in/swapped out). Time permitting I may update the blog, and with your permission use your comment)