Thank you for your reply, no mapping changes since this was first live over a year ago. The file used for the PROD and QA loads was the same set of data (in the app too). You are correct, the Production environment is a larger configuration, however, that is where the most recent run completed in over 5 hours (see below).
The time increase is in the validate source and validate intersections steps that are 'suddenly' chewing up the time. We thought maybe the audit / activity / error logs or such need to be cleaned up to help speed up that process but TBD.
We did notice that suppress zeros was false for the data source, which in our testing has helped cut the time down to about an hour, but that still does not explain the overall jump in time.
Quick update on this topic, we identified some 'corrupt' data that is causing an error when the workflow throws this message in the error log (shown below). When this occurs, the execution of the workflow impacted dramatically slows down with no other messages that have been identified. We are evaluating options to see if we can identify the 'corrupted' data outside of clearing everything and rebuilding (ideally worse case since we are in a production application). More to come...
