-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
session serialization debug can get very slow #147
Comments
Serialization should not take so much time. |
Can the session lock wait time be made visible in the logs somehow ? |
|
here is some more output then:
|
At a first look, it seems you are running debug serialization along with "production" serialization. So at the end of the request the session might be serialized both by the debugger and the servlet filter, causing locks to be held. Also, looking at some of the serialization requests, it seems timings can be very different for the same session size
To better investigate, could you please run the application only with the debugger serializer on and check if the process is still so slow? |
I have disabled the redis serialization, but it does not make a difference. |
Could you please attach the logs with redis backend disabled? |
|
It looks like most of the time is spent in deserialization.
|
@jorgheymans can you briefly describe how the UI is made up? Another thing that makes me wonder is to see an entry for |
That particular screen is 12 tabs, each with a dozen standard input fields and/or CrudGrids. There's a lot of reference data being loaded (the TranslatedCodelistItems). 179 SpringBasedBeanValidator instances seems wrong, there should not be more than about 20. We don't knowingly serialize SpringServlet though, how could it end up there? |
Did you already try to restrict the packages inspected by transient handler to see if it helps?
|
Yes, as per documentation it's set to the root package of our application. |
Hunting down a session serde problem, it was painful having to wait almost a minute between clicks for the application to settle down and stop showing the blue scrollbar. Is there anything that can be done to make this useful again?
Also, from the output you see that one sessions serde times out at 30000ms but all the others complete succesfully at 40 seconds or more. Does that indicate a bug perhaps ?
The text was updated successfully, but these errors were encountered: