ChrisHegarty commented on PR #12703:
URL: https://github.com/apache/lucene/pull/12703#issuecomment-1772974346

   > Thanks for investigating this! Can we just fix vector code to take 
MemorySegment and wrap array code?
   
   Yes, that is a good idea. I'll do it and see how poorly is performs.  If we 
do this, then we still need handle the case where a vector spans across more 
than one segment ( well, it should only ever span at most two ). We can just 
copy the bytes into a float[] for this and get a memory segment view over it - 
this will happen so infrequently.
   
   > I don't think we should add yet another factor to multiply the number of 
vector impls, there are already too many (encoding * function * cpu).
   
   Agreed.
   
   > Stuff using IndexInput can be slow and wrap arrays with MemorySegment. IMO 
we should deprecate IndexInput for lucene 10.
   
   I'm not sure how this work work, but I accept the sentiment. And I think I 
see/agree where you are going longer term with this ( and Java 22 ).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to