[sheepdog] [discuss v2] Design of Libsheepdog
Liu Yuan
namei.unix at gmail.com
Fri Jul 26 06:11:10 CEST 2013
On Fri, Jul 26, 2013 at 11:30:31AM +0800, Kai Zhang wrote:
>
> On Jul 26, 2013, at 11:25 AM, Liu Yuan <namei.unix at gmail.com> wrote:
>
> > On Fri, Jul 26, 2013 at 11:10:29AM +0800, Kai Zhang wrote:
> >>
> >> On Jul 25, 2013, at 10:36 AM, Liu Yuan <namei.unix at gmail.com> wrote:
> >>
> >>> I think we can choose a default event loop mechanism for sync API. our lib/event.c
> >>> is a good candidate for it, because it doesn't need extra library dependency and
> >>> easy to hack.
> >>
> >> I don't think we have to introduce event loop to sync API. Send data directly is simpler.
> >>
> >
> > Suppose you need to send 100M to sheep server. How can you send 100M effeciently?
> > For a dumb sync send, just you send 4M one after another. For better performance
> > you can send 25 objects in one go with async api.
> >
>
> Do you mean send 25 objects concurrently with multithreading?
Actually no, I meant true AIO that use one sender and receiver with event loop,
not threaded AIO.
Thanks
Yuan
More information about the sheepdog
mailing list