You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by nickva <gi...@git.apache.org> on 2016/11/30 06:27:42 UTC

[GitHub] couchdb-couch pull request #216: Make couchjs -S option take effect

GitHub user nickva opened a pull request:

    https://github.com/apache/couchdb-couch/pull/216

    Make couchjs -S option take effect

    Previously it was used to set JS context's stack chunk size.
    
    Instead, to be effective it should set max GC size of the runtime.
    
    Stack chunk size was set to the recommended value: 8K
    
    Reference:
    
    https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/JSAPI_reference/JS_NewContext
    
    COUCHDB-3245

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloudant/couchdb-couch couchdb-3245

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-couch/pull/216.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #216
    
----
commit 2bca9625aa6769b55520ebe796c5ccb5a55d3091
Author: Nick Vatamaniuc <va...@apache.org>
Date:   2016-11-30T05:37:12Z

    Make couchjs -S option take effect
    
    Previously it was used to set JS context's stack chunk size.
    
    Instead, to be effective it should set max GC size of the runtime.
    
    Stack chunk size was set to the recommended value: 8K
    
    Reference:
    
    https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/JSAPI_reference/JS_NewContext
    
    COUCHDB-3245

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch issue #216: Make couchjs -S option take effect

Posted by davisp <gi...@git.apache.org>.
Github user davisp commented on the issue:

    https://github.com/apache/couchdb-couch/pull/216
  
    This one: https://github.com/apache/couchdb-couch/commit/62dafe81e13d7f8e27e95057e65f76d534aa2313
    
    And make sure the rest of that commit is applied as well.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch pull request #216: Make couchjs -S option take effect

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/couchdb-couch/pull/216


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch issue #216: Make couchjs -S option take effect

Posted by jaydoane <gi...@git.apache.org>.
Github user jaydoane commented on the issue:

    https://github.com/apache/couchdb-couch/pull/216
  
    +1
    
    Though it's curious how the previous fix https://issues.apache.org/jira/browse/COUCHDB-1792 was apparently never applied. However, it clearly seems to be the right thing to do.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch issue #216: Make couchjs -S option take effect

Posted by davisp <gi...@git.apache.org>.
Github user davisp commented on the issue:

    https://github.com/apache/couchdb-couch/pull/216
  
    +1. But add a reference to Randall's commit that somehow got reverted.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch issue #216: Make couchjs -S option take effect

Posted by nickva <gi...@git.apache.org>.
Github user nickva commented on the issue:

    https://github.com/apache/couchdb-couch/pull/216
  
    Thanks @jaydoane 
    
    I think the fix was applied then switched back during a refactoring? 
    
    It is interesting why it works though. I think it probably masking a fundamental and tricky bug with garbage collection. By essentially stopping it from running.
    
    However for practical reasons we saw that at least this brings us back to behavior that we've had before in production. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch issue #216: Make couchjs -S option take effect

Posted by jaydoane <gi...@git.apache.org>.
Github user jaydoane commented on the issue:

    https://github.com/apache/couchdb-couch/pull/216
  
    Yes, maybe reverted during a refactor, since all the files that patch applied to (sm170.c, sm180.c, sm185.c) no longer exist. I guess that's easy to do with an absence of unit tests ;)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---