From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org> Subject: Re: EventMachine with thread pool and thread spawn Date: Fri, 23 Aug 2013 22:51:14 +0000 [thread overview] Message-ID: <20130823225114.GA5691@dcvr.yhbt.net> (raw) In-Reply-To: <CAA2_N1uiz7Razb5J6wYCnD0w8sXrbCRp6LnLC+hTg2+Oipfrrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> "Lin Jen-Shin (godfat)" <godfat-hOE/xeEBYYIdnm+yROfE0A@public.gmane.org> wrote: > This way, it might be easier for me to "rebase" on master. > However, I guess it might be time to give up this approach. > All tests passed except for t0106-rack-input-keepalive.sh, > but I don't find a good way to make it pass. > The key might be that pause/resume don't seem to work in > EventMachine? And using tempfile to buffer the request > might not be realistic. Yeah, t0106 is a tough one given the EM interface. Btw, has anybody sent a patch to the EM guys to allow this? (I don't do C++) > Another way would be... simply mark this model as not > suitable for large chunk pipelined requests. At least it seems > working fine on our production site. > > What do you think? That's probably fine. > Thanks for all your listening. > > (Maybe it's really time to move forward to celluloid-io, > not sure if I would get the chance to work on and finish it though..) Fwiw, nowadays my personal take these days is to avoid EM/libev*-style wrapper library unless they expose (or only have :P) a oneshot interface (EPOLLONESHOT/EV_ONESHOT). This is *especially* the case (for me) when mixing epoll/kqueue with threads. Standard event-triggered and level-triggered interfaces are both too confusing to me. Maybe it's just me, though :x _______________________________________________ Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org http://rubyforge.org/mailman/listinfo/rainbows-talk Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2013-08-23 22:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-23 21:22 Lin Jen-Shin (godfat) [not found] ` <CAA2_N1uiz7Razb5J6wYCnD0w8sXrbCRp6LnLC+hTg2+Oipfrrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2013-08-23 22:51 ` Eric Wong [this message] [not found] ` <20130823225114.GA5691-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org> 2013-08-25 12:34 ` Lin Jen-Shin (godfat) [not found] ` <CAA2_N1sqvUap-97EjpiKyLicXt3J5zeNSws3O4CAJ3VKUvgVcg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2013-08-25 21:57 ` Eric Wong [not found] ` <20130825215701.GA31966-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org> 2013-09-05 19:59 ` Lin Jen-Shin (godfat) [not found] ` <CAA2_N1utfNGSUcaNv9oLAHVzdO1MbC3wH0ar+wkfMHeCmPjkOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2013-09-05 23:03 ` Eric Wong [not found] ` <20130905230305.GA5823-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org> 2013-09-26 17:59 ` Lin Jen-Shin (godfat) 2013-09-06 6:52 ` Eric Wong
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://yhbt.net/rainbows/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20130823225114.GA5691@dcvr.yhbt.net \ --to=normalperson-rmlxzr9ms24@public.gmane.org \ --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \ --subject='Re: EventMachine with thread pool and thread spawn' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: ../../rainbows.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).