Performance issue in TastyUtil::hasTastyFile when using Java classes
See original GitHub issueHey, after I upgraded to a newer jackson version, I saw a lot of weird timeouts in our unit tests which should finish immediately.
After inspection I found this
It seems like it checks if the class has a tasty file by operating on the the jar files which is a very costly operation if we assume that this is a cpu bound operation.
It seems like this code path will always hit for classes defined in java(not scala classes), because the first two checks will always be false.
The tests succeeds if I add a retry, so I assume the result of this operation is cached?
Maybe it is possible to do val extendsScalaClass
?
Issue Analytics
- State:
- Created a year ago
- Comments:22 (11 by maintainers)
Top Results From Across the Web
Top 10 most common Java performance problems
Top 10 most common Java performance problems. 3. My career in performance began, as you might guess, with a catastrophe. I was working...
Read more >Java performance monitoring | New Relic
Learn how to improve the performance of your Java applications by optimizing your code and using a performance monitoring tool.
Read more >Performance Effects of Exceptions in Java - Baeldung
This tutorial will prove that this perception is correct and pinpoint what causes the performance issue. 2. Setting Up Environment.
Read more >Java class loading – performance impact! - Fast thread
This problem can be short-circuited, if we can load the class only once during application startup time. This can be achieved by modifying...
Read more >Classloader-Releated Memory Issues - Dynatrace
However, in Java classes, objects are managed on the heap, as well. ... memory demand without any added value and can lead to...
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 Free
Top 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
I did some testing and for non-Scala classes, there is no caching of the introspection results - meaning the work is duplicated on subsequent calls - I have added https://github.com/FasterXML/jackson-module-scala/pull/578 and it will be released when v2.14.0 is released
Thanks for clarifying, you guys are fast 😃