Thanks Uwe. > There we only use it to keep track of attributes and how to construct them. > In that case it is "write-once, read-many" and items are never deleted.
This is the key information. IIUC, the JDK performance regression is only triggered by removal - and since we don’t remove, then I would expect Lucene to be unaffected by it. -Chris. > On 26 Aug 2025, at 14:11, Uwe Schindler <[email protected]> wrote: > > Hi, > > We don't use ClassValue too extensively, only at one place: The only use of > ClassValue is in TokenStream's attribute management. There we only use it to > keep track of attributes and how to construct them. In that case it is > "write-once, read-many" and items are never deleted. So basically when a > TokenStream is constructed and attributes are added, we keep track of the > implementations responsible for all attribute classes. > > Uwe > > Am 26.08.2025 um 14:19 schrieb Luca Cavanna: >> Hey all, >> I was wondering if anyone ran Lucene benchmarks against JDK 25 so far. >> >> Based on another thread in this same list, I would assume that we ran >> successful tests but no benchmarks yet. Would it make sense to set this up >> yet or is it too early? >> >> In particular, I have some questions about >> https://bugs.openjdk.org/browse/JDK-8358535 and whether it may impact Lucene. >> >> Cheers >> Luca >> >> > -- > Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
