Code Review / mdsal.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 814ef61) | patch
Place an upper bound on notification concurrency
authorRobert Varga <rovarga@cisco.com>
Tue, 18 Feb 2014 06:43:15 +0000 (07:43 +0100)
committerRobert Varga <rovarga@cisco.com>
Tue, 18 Feb 2014 08:42:52 +0000 (09:42 +0100)
commit0495e733925b4e36a190530d13bf05a8d6529979
tree21eb9447ca6331874b860caf1d934e5e66920df3tree | snapshot
parent814ef61542a1d96f5a9b2093fc35fbd8e14bf278commit | diff
Place an upper bound on notification concurrency

In Cbench tests we have seen as many as 2000 threads being created. This
is certainly an overkill and thus let's place an upper bound on the
number of threads we create.

Change-Id: I6a7f429080504cbfa75679cc5879264a0622f140
Signed-off-by: Robert Varga <rovarga@cisco.com>
opendaylight/md-sal/sal-binding-broker/src/main/java/org/opendaylight/controller/sal/binding/codegen/impl/SingletonHolder.java diff | blob | history
MD-SAL: Model-Driven Service Adaptation Layer