Why does the debugged program slow down so much when using method entry debugging?

Question

I'm using jdi interfaces to create a debugger and when I use MethodEntryRequests to enable method entry tracing the debugged program slows down by factor of tens. I have set filter for main thread and suspend policy to SUSPEND_EVENT_THREAD. Classfilter is limited and if I print any received events it doesn't show more than couple of dozen of those so it shouldn't receive too much of them. I'm debugging locally and having followind kind of command-line with the debugged java program:

-Xdebug -Xrunjdwp:transport=dt_socket,suspend=y,server=y,address=1337

Answer 1

I would assume that the debugger needs to wake up for every method call to see if it matches the one(s) that were selected to break. Because it has to check every method call for a potential match before it can execute it is considerably slower than if it does not have to do all these checks.

Answer 2

The short answer is that execution runs through the interpreter when method entries are set. I don't think there is anyway around this...

This used to be the case for all code running in debug mode but it was enhanced in 1.4...now HotSpot works for 'full-speed' debugging except in the case of method entries and exits, watchpoints and when single stepping or in methods that contain breakpoints.

Answer 3

2 reasons:

1. it has to add checks on every method entry (there is no option to tweak just some methods)
2. method inlining becomes impossible (so small methods runs 10-100x times slower)

same goes to profilers and .net apps

Answer 4

Does running debug session in interpreted mode makes sense ? I am assuming that hop spot related benefits are not expected during a debug session.