Do anyone here have experience with what the general rule service execution performance hit of enabling integrated Blaze remote debugging is, if any?
It's quite significant - orders of magnitude slower. When you enable it, Blaze needs to send a whole lot of data from the server to your IDE and back via remote connections. It does account for that overhead when producing performance measures, but this feature is certainly pain in the neck to use on extensive basis.
Retrieving data ...