F
Frank Meulblok
Guest
"what is the performance impact?" Performance impact will depend on how many exceptions are being thrown around, and the average stack depth. But you'll see: - Increase of memory consumption, up to 32k per exception (usually far less, only a few K at most), as the exception's CallStack property will hold the callstack. - Extra processing time when an exception is thrown, as the AVM will have to unwind the stack to create the snapshot at that moment. If you want to estimate the impact for your application, try it in a test environment first. "If it's big enough to not enable it, please, share the best practice on how you find (maybe even automatically push to front-end) the place where your app failed (especially when you have a bunch of load-balanced app servers)" You could write custom messages to the appserver log from within your CATCH blocks, via LOG-MANAGER:WRITE-MESSAGE(). Gives you full control of the diagnostic info you want to write out for a given type of exception. That also costs *some* resources, but not much - from my personal experience, biggest concern there is how much disk space the extra logging will consume, and at what rate..
Continue reading...
Continue reading...