Code Review / controller.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 3ee4ced) | patch
Place an upper bound on notification concurrency 81/5381/3
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)
commit7e0482f5a2f6abed7a3af2f4313f557692a15d1d
tree92d3fd84758ecdfd21e4102e5415515c30574d97tree | snapshot
parent3ee4cedb2d45249454e1c7bfe9ad865b4cba5dcdcommit | 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
OpenDaylight controller