On Fri, Jul 6, 2018 at 2:58 AM li.penghui <[email protected]> wrote:
> But i should return the entry append success or fail for every entry. > If you can design your application leveraging asynchronous calls, you can return entry append success or fail without being blocked at waiting. > > Can I close the WAL if i can tolerate any enries lost. > I am not sure what do you mean here. > > 原始邮件 > *发件人:* Enrico Olivelli<[email protected]> > *收件人:* user<[email protected]> > *发送时间:* 2018年7月6日(周五) 16:11 > *主题:* Re: latency of bookkeeper > > Hi (your name?), > first step.... > how does your client look like ? > > WriteHandle writer = bookkeeper.createLedgerOp().....execute().get(); > > BAD WAY > writer.append() ---> SYNC, will block until fsync on bookies !!! > writer.append() ---> SYNC > writer.append() ---> SYNC > writer.append() ---> SYNC > writer.append() ---> SYNC > > GOOD WAY > writer.appendAsync() ---> ASYNC > writer.appendAsync() ---> ASYNC > writer.appendAsync() ---> ASYNC > writer.appendAsync() ---> ASYNC > writer.appendAsync() ---> ASYNC > writer.appendAsync() ---> ASYNC > writer.appendAsync().get() BLOCK ONLY ON THE last entry (or after a > batch of X entries) > > Cheers > Enrico > > > > > > Il giorno ven 6 lug 2018 alle ore 08:46 [email protected] < > [email protected]> ha scritto: > >> >> Hi >> >> I try to use bookkeeper. i care latency of write. so start >> a test in single thread. get 400 ops/s in double SSD. >> >> how to improve performance to get the low-latency. >> >> Thanks. >> >> ------------------------------ >> [email protected] >> >
