glusterfs.git/xlators/performance/write-behind/src, branch v2.0.10rc1

write-behind: fix 'option enable-trickling-writes'

2010-01-23T20:36:41+00:00

fix logic in __wb_mark_winds to properly initialize incomplete_writes
and conditionally check based on enable_trickling_writes flag

Signed-off-by: Anand V. Avati 
Signed-off-by: Anand V. Avati 

BUG: 547 (write-behind enable-trickling-writes working?)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=547

added few missing options in translator's option array

2009-10-08T04:40:14+00:00

Signed-off-by: Anand V. Avati

Changed occurrences of Z Research to Gluster.

2009-10-07T10:53:02+00:00

Signed-off-by: Anand V. Avati

write-behind: check for NULL file pointer in flush callback

2009-09-24T14:13:41+00:00

Signed-off-by: Anand V. Avati 

BUG: 260 (ls on booster VMP results in error: "File descriptor in bad state")
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=260

performance/write-behind: Add NULL checks for file pointer.

2009-09-24T12:19:37+00:00

Signed-off-by: Anand V. Avati 

BUG: 260 (ls on booster VMP results in error: "File descriptor in bad state")
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=260

performance/write-behind: Add a NULL check for request->stub before checking request->stub->fop.

2009-09-24T08:19:16+00:00

- for non-write wind requests, the request structure outlives the stub.
    The call stub is destroyed when stack is wound but request is destroyed
    only when the reply has come.
    (for writes, both stub and request are destroyed when refcount becomes 0,
     which happens only when the write operation is stack unwound and a reply
     for the write operation has come from underlying translators, for non-write
     unwind requests the request is first destroyed before resuming the stub).

Signed-off-by: Anand V. Avati 

BUG: 280 (simple stripe, with write-behind set up, when dbench is run client crashes.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=280

performance/write-behind: store currently aggregated data size in wb_file

2009-09-23T08:47:27+00:00

- this helps us to not traverse the request list whenever we need currently
    aggregated data in the queue

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

performance/write-behind: store the current window size in wb_file.

2009-09-23T08:47:23+00:00

- this would increase the performance since we don't have to traverse the
    request list every time we need the current window size.

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

performance/write-behind: reduce usage of iov_length.

2009-09-23T08:47:20+00:00

- request structure now holds a member write_size which is initialised at the
    time of request creation and used later.

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

performance/write-behind: add option "enable-trickling-writes".

2009-09-22T13:14:30+00:00

- With this option enabled, writes are stack-wound even though not enough
    data is aggregated, provided there are no write-requests which are
    stack-wound but reply is yet to come. The reason behind this option
    is to make use of the network, which is relatively free (with no writes
    or replies in transit). However, with non-standard block-sizes of writes
    the performance can actually degrade. Hence making this configurable.

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276