apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bright chen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (APEXMALHAR-2361) Optimise SpillableWindowedKeyedStorage remove(Window) to improve the performance
Date Wed, 30 Nov 2016 22:31:58 GMT
bright chen created APEXMALHAR-2361:
---------------------------------------

             Summary: Optimise SpillableWindowedKeyedStorage remove(Window) to improve the
performance
                 Key: APEXMALHAR-2361
                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2361
             Project: Apache Apex Malhar
          Issue Type: Improvement
            Reporter: bright chen
            Assignee: bright chen


Currently, SpillableWindowedKeyedStorage remove(Window) will go through each key and mark
all of them as deleted. It would be expensive when there are lots of keys and especially these
entry already spill out of memory (this the common case when remove() was called).

Suggest to mark whole window as deleted. When the window was marked as deleted, it will not
allowed to add/update any entry of this window ( this should match the requirement as remove(Window)
only be called after allowed lateness



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message