TypeMappedAnnotation.getValue(int,boolean,boolean) burns a lot of CPU, 2x total CPU usage on process after upgrade from 5.1 to 5.2
See original GitHub issueAffects: 5.2 Type: Bug
SpringFramework 5.2 has a regression in CPU performance when dealing with RequestParameter
s with default values in combination with having a Filter
that looks at the HttpServletRequest
& HttpServletResponse
(AccessLogging). The impact on CPU is massive when upgrading from 5.1
to 5.2
.
I replicated the behaviour here https://github.com/jensim/spring-boot-compare-22-21
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Reintroduce synthesized annotation attribute value caching
TypeMappedAnnotation.getValue(int,boolean,boolean) burns a lot of CPU, 2x total CPU usage on process after upgrade from 5.1 to 5.2 #24961.
Read more >Guidance for troubleshooting high CPU usage - Windows Server
This article helps you identify the cause of sustained high CPU usage. Keep in mind that you can expect CPU usage to increase...
Read more >High CPU usage kernel_task with 2 monitors - Apple Developer
The following should fix the high kernel_task CPU usage: Disconnect both external monitors. Shut down the Mac. Plug in the MagSafe power adapter...
Read more >Solved: Re: CPU Monitoring Is Disabled - NetApp Community
CPU usage can be tracked through performance counters collected by Performance Advisor. Use the CPU Utilization graph in "Storage System Summary View" to...
Read more >K28018443: After upgrade to 16.1.x, CPU usage remain high.
After upgrade /booting up from 16.1.x, odd number CPU usage went high, ... determine if the java process has datasyncd as parent process....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jensim in light of the fix for #24970, could you please try out a 5.2.6 snapshot build to see if that improves the situation for you?
Looking forward to your feedback!
See #24981