Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Fri, 3 May 2013 12:56:16 +0000 (UTC)
From: "Samuel Williams (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12639374.1364401220825.265047.1367585776315@arcas>
In-Reply-To: <JIRA.12639374.1364401220825@arcas>
References: <JIRA.12639374.1364401220825@arcas>
Subject: [jira] [Commented] (COUCHDB-1743) Make the view server & protocol
 faster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648377#comment-13648377 ] 

Samuel Williams commented on COUCHDB-1743:
------------------------------------------

Dave, makes sense. Performance is an issue. Also, the fact that the current implementation is fundamentally broken is an issue. I'm more interested in addressing the fundamentally broken part before addressing the performance part.

Specifically, improving performance of the current implementation would likely require breaking all current query servers, which would require at least as much work as what I'm suggesting in my proposal, if not more. However, in my proposal you'll note there are explicit provisions for improving the performance via extensions, which would allow performance enhancing features to be explored without fundamentally breaking the basic design.
                
> Make the view server & protocol faster
> --------------------------------------
>
>                 Key: COUCHDB-1743
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1743
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Dave Cottlehuber
>              Labels: couchdb, erlang, gsoc2013, html, javascript, nodejs, rest
>
> View server protocol enhancements/refactoring - unix sockets, pipelining, different wire format etc. Faster!!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira