In that case, create what I call a null TP profile with all TP feature boxes unchecked as shown below. Place a rule at the top of your TP policy matching the ESM traffic you wish to exclude, and put the null profile in the Action field; this will completely exclude that traffic from TP inspection. If you have more than one TP layer (not common), the rule with the null TP profile needs to be placed at the top of all of them. Note that this null profile technique is very different from a TP exception, which will not save any overhead. If this substantially improves ESM speed, you need to tune your TP configuration.
If that doesn't improve things, check your APCL/URLF rules/layer and make sure that you are not using a Destination of "Any" in those rules (use "Internet" instead) to avoid pulling this ESM traffic into the Medium path for unnecessary inspection. Also make sure that you do not have any Limit actions set in your APCL/URLF rules or the QoS blade enabled with limits configured which might be slowing down the ESM traffic.
Gateway Performance Optimization R81.20 Course
now available at maxpowerfirewalls.com