[
https://issues.apache.org/jira/browse/LUCENE-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305572#comment-17305572
]
David Smiley commented on LUCENE-9838:
--------------------------------------
Rob, is the concern that it'll be forever before Lucene requires JDK 16 or
later? Yeah. I think there are ways to mitigate that. Lucene could have a
module containing functionality that has different implementations for
different JVMs. It could be published as either a multi-release JAR file or
separate JAR files that are compatible. There's [a blog post on
gradle.com|https://blog.gradle.org/mrjars] discussing these techniques. Today,
Lucene has FutureArrays and FutureObjects classes which are kind of a baby step
to these ideas.
CC [~uschindler]
> simd version of VectorUtil.dotProduct
> -------------------------------------
>
> Key: LUCENE-9838
> URL: https://issues.apache.org/jira/browse/LUCENE-9838
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Priority: Major
> Attachments: LUCENE-9838.patch, LUCENE-9838_standalone.patch
>
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> Followup to LUCENE-9837
> Let's explore using JDK 16 vector API to speed this up more. It might be a
> hassle to try to MR-JAR/package up for users (adding commandline flags and
> stuff), but it gives good performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]