theigl opened a new issue, #2559: URL: https://github.com/apache/fory/issues/2559
### Question After running in production for several hours and no new Fory instance being created for several hours because usage is relatively uniform, I still see high load from new serializers being initialized. Here is an example: <img width="942" height="485" alt="Image" src="https://github.com/user-attachments/assets/8ed68986-cf34-43e2-899c-a3c758200f9b"; /> This class has been serialized tens of thousands of times already and almost certainly by all available instances of Fory. Any idea how this could happen? Is the `ClassResolver` reset at some point? Could registrations be evicted by GC? We are serializing thousands of different classes. Is there some limit on class registration? My config looks like this: ```java final ForyBuilder builder = Fory.builder(); builder.withName(name); builder.withClassLoader(Fory.class.getClassLoader()); builder.withBufferSizeLimitBytes(BUFFER_SIZE_LIMIT_BYTES); builder.withCompatibleMode(CompatibleMode.SCHEMA_CONSISTENT); builder.withLanguage(Language.JAVA); builder.requireClassRegistration(false); builder.withRefTracking(true); builder.withCodegen(true); builder.registerGuavaTypes(true); final var fory = (AbstractThreadSafeFory) builder.buildThreadSafeForyPool(1, poolMaxSize, 5, TimeUnit.MINUTES); ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
