couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-890) Option to use a persistent CommonJS module cache
Date Thu, 16 Feb 2012 22:43:01 GMT

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

Randall Leeds commented on COUCHDB-890:
---------------------------------------

Osher, the best way to get real-time support is to find developers in IRC in the #couchdb
room on Freenode.
The wiki has build documentation.
The main.js script the server runs is in the directory share/server. Those files are all concatenated
at build time (see Makefile.am in that directory) and output to the file main.js.
To debug you can try to run the file directly with the couchjs program and pretend to be the
CouchDB side of the View Server Protocol, which you can also find on the wiki.
                
> Option to use a persistent CommonJS module cache
> ------------------------------------------------
>
>                 Key: COUCHDB-890
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-890
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>         Environment: All
>            Reporter: mikeal
>         Attachments: commonjscache.diff
>
>
> Since COUCHDB-1075, there is a CommonJS module cache used for resolving circular CommonJS
dependencies. However, Caolan reports a 10x speed improvement by not clearing this cache between
requests. An option to not clear the cache could be a great tool for performance-interested
power users who know their CommonJS modules are sane. The improvement will be even greater
when we turn on the JIT compiler in SpiderMonkey since cached modules will benefit from being
pre-JIT'd.

--
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

        

Mime
View raw message