This is introduced by a recent fix [1]. It seems forcing writes when ResultState is being closed should give same semantics (but with much higher throughput)?
[1] https://asterix-gerrit.ics.uci.edu/#/c/2319/ On Mon, Apr 2, 2018 at 10:27 AM, Chen Luo <[email protected]> wrote: > Hi Devs, > > As I saw last week, using the "sync" write mode to write data (i.e., in > Transaction Log Flusher) can lead to bad write throughput if the write > buffer is small. However, I just saw "sync" write mode is in ResultState > when we store the query result [1]. *Is this "sync" mode really needed on > a frame-basis*? The frame size is typically 32KB, and this could lead to > low throughput if a user wants to pull a lot of data out of our system. If > there is no specific need for this "sync" write, I'll submit a change to > fix it. Thanks! > > [1] https://github.com/apache/asterixdb/blob/ > 77c8c79077ec33fae5944d982a337b784608aa87/hyracks-fullstack/ > hyracks/hyracks-control/hyracks-control-nc/src/main/ > java/org/apache/hyracks/control/nc/dataset/ResultState.java#L130 > > Best regards, > Chen Luo >
