You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Zach Chen (Jira)" <ji...@apache.org> on 2021/05/06 06:19:00 UTC
[jira] [Commented] (LUCENE-9662) CheckIndex should be concurrent
[ https://issues.apache.org/jira/browse/LUCENE-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340017#comment-17340017 ]
Zach Chen commented on LUCENE-9662:
-----------------------------------
Hi [~mikemccand], I've taken a stab at this and created a WIP PR [https://github.com/apache/lucene/pull/128] with some nocommit comments. Could you please take a look and let me know your thoughts?
> CheckIndex should be concurrent
> -------------------------------
>
> Key: LUCENE-9662
> URL: https://issues.apache.org/jira/browse/LUCENE-9662
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Priority: Major
>
> I am watching a nightly benchmark run slowly run its {{CheckIndex}} step, using a single core out of the 128 cores the box has.
> It seems like this is an embarrassingly parallel problem, if the index has multiple segments, and would finish much more quickly on concurrent hardware if we did "thread per segment".
> If wanted to get even further concurrency, each part of the Lucene index that is checked is also independent, so it could be "thread per segment per part".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org