diff options
| author | Thomas Watson | 2019-04-09 18:13:14 +0000 |
|---|---|---|
| committer | Thomas Watson | 2019-04-12 13:58:21 +0000 |
| commit | 2e8fc7a7f648e3ad325e55863aca098c8e108db6 (patch) | |
| tree | 572bb72a7f16728e84a0f3411c22700e0135d8fc /.gitattributes | |
| parent | e98581771affe7d6ae47902670bacc572b0a9e75 (diff) | |
| download | rt.equinox.framework-2e8fc7a7f648e3ad325e55863aca098c8e108db6.tar.gz rt.equinox.framework-2e8fc7a7f648e3ad325e55863aca098c8e108db6.tar.xz rt.equinox.framework-2e8fc7a7f648e3ad325e55863aca098c8e108db6.zip | |
Bug 540507 - parallel activation of bundles from framework start-level
By default the framework start-level implementation activates all
bundles that have the same start-level in sequential order using the
bundle ID (install order) to determine the order the bundles are started
from a single thread.
A new configuration option is added equinox.start.level.thread.count
that is set to 1 by default. This will cause the framework to continue
with the behavior of activating all bundles with a single thread.
If equinox.start.level.thread.count is set to -1 then the framework will
use an executor with the number of threads == to
java.lang.Runtime.availableProcessors() to activate the bundles in
parallel. This means that the order the bundles with the same
start-level are activated becomes random. The
equinox.start.level.thread.count config setting can also be set to a
value > 1 to give an explicit value for the number of threads to use
(instead of using java.lang.Runtime.availableProcessors() to determine
the number)
Change-Id: Ifcf6f18b762bcb114f8f8c75630fdca0cb79a24c
Signed-off-by: Thomas Watson <tjwatson@us.ibm.com>
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions