couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Smith <...@iriscouch.com>
Subject Re: [jira] [Commented] (COUCHDB-1342) Asynchronous file writes
Date Fri, 18 Nov 2011 03:43:07 GMT
On Fri, Nov 18, 2011 at 10:06 AM, Damien Katz (Commented) (JIRA)
<jira@apache.org> wrote:
> Right now we have a culture of everyone's pet concerns must addressed before code gets
checked in, which is demoralizing and slows things down, which is a very big problem the project
has right now. I want your help in trying to change that.

I'm sorry to agree. I made two (IMO) useful contributions and both
died in JIRA committee.

My CORS implementation[1] was ignored for three months (15 May - 24
August), despite production deployment at Iris Couch. Ultimately, a
competing patch showed up, with no reason given. After some
discussion, it too languishes.

My inbox database feature[2] is suffering the same fate. Both features
are highly requested by real-world Couch app developers.

I have a new CommonJS feature mostly done but I've postponed it.

(I'm not changing the subject, just sharing that it's not just newbies
who are frustrated. I'm not super frustrated, just a little
frustrated.)

My inbox database patches[2] are also
[1]: https://issues.apache.org/jira/browse/COUCHDB-431

The last two big contributions I made have been ignored in JIRA. My
CORS implementation[1] was ignored
>
>> Asynchronous file writes
>> ------------------------
>>
>>                 Key: COUCHDB-1342
>>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1342
>>             Project: CouchDB
>>          Issue Type: Improvement
>>          Components: Database Core
>>            Reporter: Jan Lehnardt
>>             Fix For: 1.3
>>
>>         Attachments: COUCHDB-1342.patch
>>
>>
>> This change updates the file module so that it can do
>> asynchronous writes. Basically it replies immediately
>> to process asking to write something to the file, with
>> the position where the chunks will be written to the
>> file, while a dedicated child process keeps collecting
>> chunks and write them to the file (and batching them
>> when possible). After issuing a series of write request
>> to the file module, the caller can call its 'flush'
>> function which will block the caller until all the
>> chunks it requested to write are effectively written
>> to the file.
>> This maximizes the IO subsystem, as for example, while
>> the updater is traversing and modifying the btrees and
>> doing CPU bound tasks, the writes are happening in
>> parallel.
>> Originally described at http://s.apache.org/TVu
>> Github Commit: https://github.com/fdmanana/couchdb/commit/e82a673f119b82dddf674ac2e6233cd78c123554
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>



-- 
Iris Couch

Mime
View raw message