Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

added remark about dynamically created server threads

This commit is contained in:
Frank Celler 2014-11-12 04:37:02 +01:00
parent f74849611d
commit badbf916cf
2 changed files with 28 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
CHANGELOG
View File

@ -1,4 +1,4 @@
v2.3.0-beta2 (2014-11-01) 2.3.0-beta2 (2014-11-01)
------------------- -------------------
* front-end: new icons for uploading and downloading JSON documents into a collection * front-end: new icons for uploading and downloading JSON documents into a collection
@ -86,22 +86,23 @@ v2.3.0-beta2 (2014-11-01)
V8 contexts created in arangod. V8 contexts created in arangod.
Previously, the number of V8 contexts was equal to the number of server threads Previously, the number of V8 contexts was equal to the number of server threads
(as specified by option `--server.threads`). However, it may be sensible to (as specified by option `--server.threads`).
create different amounts of threads and V8 contexts. If the option is not
specified, the number of V8 contexts created will be equal to the number of
server threads. Thus no change in configuration is required to keep the old
behavior.
However, the default configuration files shipped with ArangoDB have been changed.
The number of server threads has been increased in the configuration files, and
the number of V8 contexts is now explicitly set in the configuration files (to
the same value as the number of server threads was set to in 2.2).
If you are using the default config files or merge them with your local config files, However, it may be sensible to create different amounts of threads and V8
please review if the higher default number of server threads is okay in your contexts. If the option is not specified, the number of V8 contexts created
will be equal to the number of server threads. Thus no change in configuration
is required to keep the old behavior.
If you are using the default config files or merge them with your local config
files, please review if the default number of server threads is okay in your
environment. Additionally you should verify that the number of V8 contexts environment. Additionally you should verify that the number of V8 contexts
created (as specified in option `--javascript.v8-contexts`) is okay. created (as specified in option `--javascript.v8-contexts`) is okay.
* the number of server.threads specified is now the minimum of threads
started. There are situation in which threads are waiting for results of
distributed database servers. In this case the number of threads is
dynamically increased.
* removed index type "bitarray" * removed index type "bitarray"
Bitarray indexes were only half-way documented and integrated in previous versions Bitarray indexes were only half-way documented and integrated in previous versions

28
Documentation/Books/Users/Upgrading/UpgradingChanges23.mdpp
View File

@ -6,10 +6,15 @@ upgrading to ArangoDB 2.3, and adjust any client programs if necessary.
!SECTION Default configuration file changes !SECTION Default configuration file changes
With ArangoDB 2.3, the number of server threads can be configured independently of The number of server threads specified is now the minimum of threads
the number of V8 contexts. The configuration option `--javascript.v8-contexts` was started. There are situation in which threads are waiting for results of
added to arangod to provide better control over the number of V8 contexts created distributed database servers. In this case the number of threads is dynamically
in arangod. increased.
With ArangoDB 2.3, the number of server threads can be configured independently
of the number of V8 contexts. The configuration option
`--javascript.v8-contexts` was added to arangod to provide better control over
the number of V8 contexts created in arangod.
Previously, the number of V8 contexts arangod created at startup was equal Previously, the number of V8 contexts arangod created at startup was equal
to the number of server threads (as specified by option `--server.threads`). to the number of server threads (as specified by option `--server.threads`).
@ -19,18 +24,13 @@ and V8 contexts. This is because each V8 contexts created will consume memory
and requires CPU resources for periodic garbage collection. Contrary, server and requires CPU resources for periodic garbage collection. Contrary, server
threads do not have such high memory or CPU footprint. threads do not have such high memory or CPU footprint.
If the option `--javascript.v8-contexts` is not specified, the number of V8 If the option `--javascript.v8-contexts` is not specified, the number of V8
contexts created at startup will remain equal to the number of server threads. contexts created at startup will remain equal to the number of server threads.
Thus no change in configuration is required to keep the same behavior as in Thus no change in configuration is required to keep the same behavior as in
previous ArangoDB versions. previous ArangoDB versions.
However, the default configuration files shipped with ArangoDB have been changed. If you are using the default config files or merge them with your local config
The number of server threads has been increased in the configuration files, and files, please review if the default number of server threads is okay in your
the number of V8 contexts is now explicitly set in the configuration files (to
the same value as the number of server threads was set to in 2.2).
If you are using the default config files or merge them with your local config files,
please review if the higher default number of server threads is okay in your
environment. Additionally you should verify that the number of V8 contexts environment. Additionally you should verify that the number of V8 contexts
created (as specified in option `--javascript.v8-contexts`) is okay. created (as specified in option `--javascript.v8-contexts`) is okay.