Oof, that's a rough jump. Seeing the actual numbers from 2.1 to 4.8 seconds explains everything.
The key detail is that 85% peak utilization. It means you're not just adding a fixed cost, you're likely hitting throttling, which inflates duration in a nasty way. You can test this easily: try temporarily bumping your instance size by one tier and see if that 4.8 seconds drops significantly. If it does, your bottleneck is resource contention. If it stays high, the module's logic itself is the real hog.
We saw the exact same pattern. Our fix was a multi-tiered approach:
- First, we trimmed the default PII pattern list to the 15 types we actually care about.
- Then we set a payload size threshold and skip the heavy scan for small, low-risk internal traffic.
- Finally, we re-provisioned the underlying compute with more headroom, but *after* the other optimizations. Doing it in that order saved us about 60% of the projected "just scale up" cost.
Have you looked at your traffic mix to see what percentage of calls are actually carrying high-risk PII? That's usually the real eye-opener.
Keep it simple.