poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 61862] Improve TreeMap implementation to cache first and last key
Date Wed, 06 Dec 2017 23:46:01 GMT

--- Comment #2 from Greg Woolsey <gwoolsey@apache.org> ---
How about caching the first and last keys and a "dirty" flag or clearing the
cache values on structural changes?  Then the first/last would only need to be
calculated on first access after changes.  I can see these being referenced
many times when evaluating formulas, for example, but we wouldn't want them to
be continuously updated as rows are being created.  Lazy init, eager
clearing/dirtying would perhaps still offer a formula performance gain without
adding much if any overhead when creating documents.

The only cases where it wouldn't add much value, and still wouldn't add much
overhead beyond what TreeMap already does, would be cases where data changes
and formula evaluations/data scanning are done repeatedly or in some
iterative/interleaved pattern.  In my experience these are not typical use

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org

View raw message