zhenjl

12 ms·

31.
A Modern App Developer and an Old-Timer System Developer Walk into a Bar(zhen.org)
148 points by zhenjl 11y ago|82 comments
32.
2016: Analyzing Security Trends Using RSA Exhibitor Descriptions(zhen.org)
2 points by zhenjl 11y ago|0 comments
33.
by zhenjl 11y ago
Should call it 1fs with the number 1. 1fs.io is even avail!
34.
Habits of Unicorn Entrepreneurs(huffingtonpost.com)
3 points by zhenjl 11y ago|0 comments
35.
Analyzing Security Trends Using RSA Exhibitor Descriptions(zhen.org)
2 points by zhenjl 12y ago|0 comments
36.
Sequence: Scanning and Tokenizing 200-500K Log Messages per Second(zhen.org)
2 points by zhenjl 12y ago|0 comments
37.
Sequence: Optimizing Go for the High Performance Log Scanner(zhen.org)
2 points by zhenjl 12y ago|0 comments
38.
Sequence: Automated Analyzer for Reducing Log Messages to Patterns(zhen.org)
37 points by zhenjl 12y ago|0 comments
39.
by zhenjl 12y ago
Thanks for letting me know. I hadn't realized that. Will have to figure out why.
40.
by zhenjl 12y ago
I don't have any first hand experience, but it seems like grok [might not be that performant]( http://ghost.frodux.in/logstash-grok-speeds/ )?
41.
by zhenjl 12y ago
Thanks for the link. Do you have any info on the performance of this parser?
42.
Sequence: A High Performance Sequential Semantic Log Parser at 175,000 MPS(zhen.org)
21 points by zhenjl 12y ago|8 comments
43.
ScriptRock's Experience with Go, After Porting 30KLOC(scriptrock.com)
8 points by zhenjl 12y ago|1 comments
44.
Generating Porter2 FSM for Fun and Performance in Go(zhen.org)
1 points by zhenjl 12y ago|0 comments
45.
My Perspective on Go(zhen.org)
52 points by zhenjl 12y ago|27 comments
46.
by zhenjl 12y ago
Try a static blog generator like hugo or octopress...
47.
Sequence: A High Performance Sequential Semantic Log Analyzer and Parser(zhen.org)
2 points by zhenjl 12y ago|0 comments
48.
PingMQ: A SurgeMQ-based ICMP Monitoring Tool(zhen.org)
3 points by zhenjl 12y ago|0 comments
49.
by zhenjl 12y ago
I ran with GOMAXPROCS=2 on the command line. The post showed the actual commands that I used in each case.
50.
by zhenjl 12y ago
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 Mac OS Yosemite..
51.
by zhenjl 12y ago
Ah..k...no peeking beyond just the head of the queue.
52.
by zhenjl 12y ago
Heh. No worries. Excellent list of questions. Like antirez, I am evernoting (is that a verb now?) this for future references.
53.
by zhenjl 12y ago
When I ran this I gave the server and client 2 cores each. Neither were maxing out the cores. At about 856K MPS (sent + received) @ 1024 bytes/msg, that's less than 1 GBps. So I can't imagine it being io(net) bound either. So
54.
by zhenjl 12y ago
I have not. But I am going to assume you are telling me to learn more about how to calculate my performance numbers. :) Fair point and I will bookmark for future reading.
55.
by zhenjl 12y ago
Author here. The message size tested is 1024 bytes.
56.
by zhenjl 12y ago
Excellent question regarding latency. Tyler Treat who wrote an excellent blog post on MQ performance tested this and got mean latency for 1000000 messages of 98.751015 ms. https://github.com/tylertreat/mq-benchmarking&#
57.
by zhenjl 12y ago
Author here. A bit of a pleasant surprise to wake up and see this on HN. Thanks for the detailed response. Here's some answers hopefully can help clarify things a bit. * Are messages delivered once and only once? A: MQTT allows QoS 0 (
58.
by zhenjl 12y ago
Author here. There's really no comparison tbh. RabbitMQ has been battle tested for years and SurgeMQ is just at its infancy. And RabbitMQ has a lot more enterprise security features that SurgeMQ doesn't have today. So if you are l
59.
Getting good performance in Go by rewriting parts in C?(lemire.me)
2 points by zhenjl 13y ago|0 comments
60.
by zhenjl 13y ago
Did you by chance profile the Go program to see where the hot spots are?

More ›