mikemccand commented on PR #13572: URL: https://github.com/apache/lucene/pull/13572#issuecomment-3050061148
Thanks @shubhamvishu -- these results look incredible, if they hold up. Odd that Panama Vector API (which Lucene uses for `dotProduct`) is so much slower on Graviton2. It's also odd that indexing throughput got a bit slower with the change? Much of the indexing cost for HNSW is actually searching (each insert is searching for top K vectors in the graph, so far, and adding those as edges for this vector's node)? Oh, actually, in one run (baseline) you had 3 segments, and then later with candidate 2 segments, odd. I really want the simple Python tool that I can run in my prod env and it tells me "yes, Lucene HNSW Is using optimal SIMD instructions in your JDK, Lucene version, OS, CPU architecture/revision, virtualized environment, etc." -- I opened luceneutil issue to try to make progress on this: https://github.com/mikemccand/luceneutil/issues/421 ... maybe `perf` tool can give us counters of how many of which CPU asm instructions are used or so? -- 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
