15

I was wondering if there are any major performance issues with using AspectJ if it is being used to intercept every (or just most) method in an application. Of course, performance would also be affected by the advice that got executed on every interception.

For the sake of this example, let's say its very simple advice that runs very quickly and with minimal overhead/no memory leaks. Are there still significant performance killers since every method is being intercepted?

IAmYourFaja
  • 55,468
  • 181
  • 466
  • 756
  • The overhead of what you do in the interception could be much higher unless its trivial. E.g. if you log to a file, that will be much higher. – Peter Lawrey Jan 16 '12 at 13:55
  • 1
    Are you using compile-time or runtime weaving? – mazaneicha Jan 16 '12 at 14:01
  • 2
    possible duplicate of [Performance impact of using aop](http://stackoverflow.com/questions/433475/performance-impact-of-using-aop) – Balder Jan 08 '15 at 09:41

1 Answers1

2

It certainly won't accelerate your code. I've seen horrible results where 19 stackframes had been added between a caller and a callee for an otherwise direct rapid event handling method. Suffice to say AOP is dead in my mind.

If you are lucky, you may have compiled code, which is inlined by the jit compiler and merely adds the actual work you chose to add as if you wrote it in place. Worst cases, like the spring/osgi crap out there, you end up with some unusable snail.

user2023577
  • 1,752
  • 1
  • 12
  • 23