You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ignacio Vera (JIRA)" <ji...@apache.org> on 2019/02/20 11:20:00 UTC
[jira] [Resolved] (LUCENE-8699) Use fixed byte array in
HeapPointWriter
[ https://issues.apache.org/jira/browse/LUCENE-8699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ignacio Vera resolved LUCENE-8699.
----------------------------------
Resolution: Fixed
Assignee: Ignacio Vera
Fix Version/s: master (9.0)
8.x
> Use fixed byte array in HeapPointWriter
> ---------------------------------------
>
> Key: LUCENE-8699
> URL: https://issues.apache.org/jira/browse/LUCENE-8699
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Ignacio Vera
> Assignee: Ignacio Vera
> Priority: Major
> Fix For: 8.x, master (9.0)
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
>
> {heapPointWriter} is always created with the same init size and max size. It might make sense to change the implementation to use a byte array instead of a growable structure as it has now. This seems to improve performance:
>
> ||Approach||Index time (sec): Dev||Index Time (sec): Base||Index Time: Diff||Force merge time (sec): Dev||Force Merge time (sec): Base||Force Merge Time: Diff||Index size (GB): Dev||Index size (GB): Base||Index Size: Diff||Reader heap (MB): Dev||Reader heap (MB): Base||Reader heap: Diff||
> |points|122.1s|147.0s|-17%|51.9s|70.5s|-26%|0.55|0.55|0%|1.57|1.57|0%|
> |shapes|211.1s|244.6s|-14%|121.1s|135.0s|-10%|1.29|1.29|0%|1.61|1.61|0%|
> |geo3d|154.2s|186.6s|-17%|63.4s|82.8s|-23%|0.75|0.75|0%|1.58|1.58|0%|
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org