Viewing profile — kerr23
kerr23
HN member- Joined
- Wed, Jul 09, 2014, 9:50 PM UTC
- HN karma
- 60
- Public activity
- 22 items
- HN profile
- View on Hacker News ↗
About kerr23
No profile information was provided.
Recent public activity
-
comment
Comment #32779172
I worked for Baan at that time, that was one of the selling points. Baan still exists as Infor ERP Ln
-
comment
Comment #32527400
I did the same, originally planned on UniFi but since i couldn’t get any i tried Omada. It’s very nice, the only issue i’ve had is my mesh not connecting, but i solved that by reor…
-
comment
Comment #29709873
Anyone have any luck trying to bing / google “challenge to do” and get that result? I didn’t find it after a couple variations. Also any reason to believe that the tweet was true? …
-
comment
Comment #16835980
> Why doesn't 'software architect' get the same criticism for not being an architect? I'm married to an Architect, it bugs them too. In most states - Legally they can't call themse…
-
comment
Comment #15798831
Be prepared to take advantage of it. Downturns are basically sales.
-
comment
Comment #11942772
> My real complaint is that none of these give you a way to do persistence that doesn't destroy some other really nice properties of containers. 100% agree with you there. > It mos…
-
comment
Comment #11941943
hmm, your first complaint was that "Swarm offers no guarantees that containers will be rescheduled on the same host". I'm saying that, if you want, you CAN make it guarantee that a…
-
comment
Comment #11941378
In docker 1.12 you can 'tag' a node and tell a 'service' to only run on the tagged nodes. Not saying that's a good idea, but it is getting closer. You could, for example, have a no…
-
comment
Comment #11884494
I'm impressed that the reporter did a whois search and tried various domains. That's not something I would expect from a standard US reporter now-a-days.
-
comment
Comment #11348370
Lynch's Dune is one of my all time favourite movies. I watched it a lot growing up and it didn't make a lick of sense to me, but I still loved the world it created. Later on I saw …
-
comment
Comment #10578694
AWS is always super closed mouthed about their infrastructure. The info I have came from a conversation with an AWS Solutions Architect. It's a couple of years old, but based on my…
-
comment
Comment #10578691
DNS was precisely the area where we got bit by it. We were using a Non-AWS DNS resolver (aka Google) and we would often get dns resolution errors despite our NAT not being remotely…
-
comment
Comment #10578336
AWS de-prioritizes UDP packets making it not a great choice for UDP based applications as well.
-
comment
Comment #10361661
Didn't recognize L'il Sebastian. Total Fail. =)
-
comment
Comment #8639070
I moved between being a life-long vi/vim'er to Sublime and more recently Atom. I only use Atom for coding and vim for just about everything else. The most difficult part for me is …
-
comment
Comment #8015035
I did a control benchmark between PG Ubuntu vs PG on CentOS, the results are in the post.
-
comment
Comment #8015024
Well, Docker is big news and people are interested in what the performance impact of "using docker" is. Whether it's accurate or not, people associate Docker with the functionality…
-
comment
Comment #8013097
Incidentally. Now that I look at who's post I replied to. Obviously you know about --volume vs VOLUME. I've updated the blog post to specify that since it was obviously unclear.
-
comment
Comment #8013072
I ran the benchmark multiple times and I got very consistent results. I know that doesn't eliminate the VM factor, but it certainly minimizes it. Also, this test wasn't meant to be…
-
comment
Comment #8012496
I ran all of the benchmarks on the same machine. I would see it possible that the pre-configured Digital Ocean machine favors docker processes over non-docker somehow.
-
comment
Comment #8012476
Mentioned above that i started the container with --volume. The 3 docker conditions where No flags, --volume /.../, --volume /.../ --net=host
-
comment
Comment #8012460
Howdy. I'm the author of the blog post. I started the container with --volume in the case of "docker with no virtual I/O" Which is the same as setting VOLUME in your Dockerfile.