theigl commented on issue #2559: URL: https://github.com/apache/fory/issues/2559#issuecomment-3253041161
Unfortunately not. After running in production for a couple of hours, my serializer pool has stabilized and all Fory instances have encountered most classes. Now my logs show one or two serializers being created for rarer classes every couple of minutes. That's exactly what I would have expected. However, my profiler still shows high load from creating serializers: <img width="931" height="320" alt="Image" src="https://github.com/user-attachments/assets/36bbf6d1-a0ac-4c6c-ad2b-25f51a35b155"; /> I use a custom `SerializerFactory` to log attempts to create new serializers but nothing shows up in my logs. I don't understand how this can happen, because I don't see a code path that invokes `DisallowedList.checkNotInDisallowedList()` and then bypasses my custom `SerializerFactory`. I'm afraid I will have to build a custom version of `Fory` that adds much more logging. -- 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]
