You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Roshan Naik (JIRA)" <ji...@apache.org> on 2018/06/10 11:10:00 UTC
[jira] [Updated] (STORM-3100) Minor optimization: Replace
HashMap with an array backed data structure for faster lookups
[ https://issues.apache.org/jira/browse/STORM-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roshan Naik updated STORM-3100:
-------------------------------
Summary: Minor optimization: Replace HashMap<Integer, T> with an array backed data structure for faster lookups (was: Minor optimization: Replace HashMap<Integer, T> in critical path with an array backed data structure for faster lookups)
> Minor optimization: Replace HashMap<Integer, T> with an array backed data structure for faster lookups
> ------------------------------------------------------------------------------------------------------
>
> Key: STORM-3100
> URL: https://issues.apache.org/jira/browse/STORM-3100
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Roshan Naik
> Priority: Major
>
> * Introduce _CustomIndexArray_: An array backed data structure to replace HashMap<Integer, T> use cases. So it needs to supported -ve indexing. Does not need to be dynamically resizable given the nature of use cases we have. Upper and lower Index range needs to be specified at construction time.
> * Use this data structure for _GeneralTopologyContext._taskToComponent_ mapping which is looked up in the critical path _Task.getOutgoingTasks._ This lookup happens at least once for every emit and consequently can happen millions of times per second.
> * Also use this for _JCQueue.localReceiveQueues_ where the basic idea is already in use but not in a reusable manner.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)