Viewing profile — kqueue
kqueue
HN member- Joined
- Sun, Apr 11, 2010, 7:23 AM UTC
- HN karma
- 265
- Public activity
- 206 items
- HN profile
- View on Hacker News ↗
About kqueue
No profile information was provided.
Recent public activity
- story
- story
-
comment
Comment #3330806
I tried using SC2 (aka Amber), while it has a lot of potential and I love the powerful binding mechanism it has, it simply lacked documentation and support. I hope Amber has tackle…
-
comment
Comment #3291965
Line numbers missing.
-
comment
Comment #3262590
I feel the word rubs you the wrong way and you are trying to come up with arguments to support your emotions.
-
comment
Comment #3259636
I would put some effort and change the default bootstrap css theme because it looks like many other websites.
-
comment
Comment #3214531
I don't know you and what you say won't give you more credibility. Your points are subjective because they fall under theories. Don't point them out like facts.
-
comment
Comment #3209644
All your points are subjective.
-
comment
Comment #3189020
reminds me of http://chirpme.com/
-
comment
Comment #3184282
I don't like fixed position UI and scrolling within a small section. I prefer the whole page to scroll. I am staying on the old version.
-
comment
Comment #3170223
I totally agree that SYSCALL/SYSENTER/SYSRET are very cheap to execute. But these instructions only takes care of the ring switch and are not executed alone. When you make a system…
-
comment
Comment #3167437
I didn't say there is no distinction. I said system calls that require disk io, or network io, or triggers locking/sleeping requires a context switch. Calls like read/write/accept …
-
comment
Comment #3167352
Network IO, Disk IO, scheduling, locks etc.. all trigger context switches and not only mode switch because only the kernel is allowed to manipulate data structures related to mbufs…
-
comment
Comment #3166876
request rate is not influenced much by the polling mechanism (epoll/kqueue/poll/select) when all you're doing is listening to one fd and processing new ones then closing then immed…
-
comment
Comment #3166271
Measuring requests per second is close to measuring the number of accept system calls you can do. Since it's a system call you have a context switch.
-
comment
Comment #3166180
I believe you are testing the requests / sec and not replies / sec. While requests / sec matters a bit, you'll most probably be bottle-necking in your context switches. What matter…
-
comment
Comment #3166012
I see. I haven't tried them personally, my friend has been using them for a year now and so far so good. He did complain about their support though.
-
comment
Comment #3165894
This service provider has great pricing compared to softlayer http://www.hetzner.de/en/hosting/produktmatrix/rootserver-pr... Intel Corei7-2600 Quad core + 16GB DDR3 + 2 x 3TB 7200…
-
comment
Comment #3138243
That's why you should start from the finish line and move backwards.
-
comment
Comment #3122627
From the polls that happened in the past, I saw more votes in favor of showing scores.
-
comment
Comment #3114314
repost.
-
comment
Comment #3076877
Not to mention that kevent contain the number of bytes to be read, or the number of connections to accept, which can avoid you a system call that returns EAGAIN in a non-blocking s…
-
comment
Comment #3073529
1. Process creation and termination are heavy operations considering that it's being done in a tight loop. 2. You don't want to fork on every request, this is very vulnerable to fo…
-
comment
Comment #3073465
No that's not the proper way of doing it. You create worker threads in separate process that receive data from node.js, encodes them and send them back. you don't fork on every req…
-
comment
Comment #3065293
This is where gcd can help. http://en.wikipedia.org/wiki/Grand_Central_Dispatch