View Revisions: Issue #3792
| Summary | 0003792: Routing bottleneck on long routing runs | ||
|---|---|---|---|
| Revision | 2019-04-04 18:20 by mmichalek | ||
| Description | My understanding is that ChannelRouterContext HashSet was only there for logging/diagnostic purposes. Removing the transactions HashSet. Observed code hotspot in routing: source-router-reader-1 java.util.HashMap.hash():338 java.util.HashMap.put():611 java.util.HashSet.add():219 org.jumpmind.symmetric.route.ChannelRouterContext.addTransaction():265 org.jumpmind.symmetric.route.DataGapRouteReader.execute():203 org.jumpmind.symmetric.route.DataGapRouteReader.run():129 java.util.concurrent.ThreadPoolExecutor.runWorker():1142 java.util.concurrent.ThreadPoolExecutor$Worker.run():617 java.lang.Thread.run():745 |
||
| Revision | 2018-11-13 18:45 by mmichalek | ||
| Description | Observed code hotspot in routing: source-router-reader-1 java.util.HashMap.hash():338 java.util.HashMap.put():611 java.util.HashSet.add():219 org.jumpmind.symmetric.route.ChannelRouterContext.addTransaction():265 org.jumpmind.symmetric.route.DataGapRouteReader.execute():203 org.jumpmind.symmetric.route.DataGapRouteReader.run():129 java.util.concurrent.ThreadPoolExecutor.runWorker():1142 java.util.concurrent.ThreadPoolExecutor$Worker.run():617 java.lang.Thread.run():745 |
||