rmuir commented on issue #14408: URL: https://github.com/apache/lucene/issues/14408#issuecomment-2830144654
> +1 to work towards this more general fix. But, sheesh, it looks so complicated, depending on hot vs cold use case, preloading or not, which part of the Lucene index (KNN, terms, postings), Linux kernel versions, ... in the mean time I think we should revert back to `NORMAL`/`DEFAULT` as Lucene's default... Yes, my argument is that it is complicated, and lucene needs to get out of the business of it. We can flip-flop on this setting over and over again, and each time some users will experience regressions and others will get happy. I don't want to see this, it is just more of the same. Lucene needs to get out of the business of doing it. But if you want a quick fix: I'd be in favor of a PR that removes all madvise/preloading/otherwise from lucene. Let it be the "user's decision" on this shit, the different use-cases and platforms are too different, lucene cannot have "defaults" in java code and pretend like thats gonna work well across all these various use-cases and platforms. it does not work. and for users that care and want this stuff, hopefully it gets easier for them once #14422 lands. This way its not constant regressing back and forth because of settings flipflopping -- 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
