CODEWITHSUNDEEP
javaspring
imrichardcole
imrichardcole

Reputation: 4685

Timings with Spring application contexts

I'm currently trying to track down a performance issue and I've found a large amount of time is being spent in the code where you request a bean from a ApplicationContext:

ApplicationContext.getBean(String beanName);

Do you know if it's possible to turn on any debug or log information within Spring so that I can see all the objects that are instantiated from this call as well as the times to create them?

I've been trying to profile with Yourkit, but the operation only take 1.4 seconds in total and only on the first call, so Yourkit seems to struggle with short lived, one off calls like this.

It's why I was heading down the logging route.

Upvotes: 1

Views: 78

Answers (1)

duffymo
duffymo

Reputation: 308763

Spring uses log4j, so you can set your log level to debug and see what you get. It'll be a lot of output. I'd advice not logging it to the console - write it to a file.

How did draw that conclusion? Are you profiling your app with Visual VM, with all the plugins installed?

I'd bet that the app context is not the issue. If the time spent in the app context is large, it should just be on startup when Spring is reading and parsing the configuration, instantiating and wiring beans. Once it's done the cost is amortized over the life of your app. For most web apps this is a startup cost, not a reflection on the experience users have when using your site.

It's far more likely to be in your code. Be sure that you aren't being mislead by not taking a comprehensive view.

Upvotes: 3

Related Questions