lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LUCENE-2422) don't reuse byte[] in IndexInput/Output for read/writeString
Date Tue, 04 May 2010 18:57:56 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael McCandless resolved LUCENE-2422.
----------------------------------------

    Resolution: Fixed

> don't reuse byte[] in IndexInput/Output for read/writeString
> ------------------------------------------------------------
>
>                 Key: LUCENE-2422
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2422
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.9.3, 3.0.2, 3.1, 4.0
>
>         Attachments: LUCENE-2422.patch
>
>
> IndexInput now holds a private "byte[] bytes", which it re-uses for reading strings.
 Likewise, IndexOutput holds a UTF8Result (which holds "byte[] bytes"), re-used for writing
strings.
> These are both dangerous, since on reading or writing immense strings, we never free
this storage.
> We don't use read/writeString in very perf sensitive parts of the code, so, I think we
should not reuse the byte[] at all.
> I think this is likely the cause of the recent "IndexWriter and memory usage" thread,
started by Ross Woolf on java-user@.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message