Update on this: support agreed there is some defect affecting performance, and assigned the severity as U4. I’ll see how long it takes for them to fix it, but we told them the change orders need to be fully created before the 29th of March, which is only 18 days away

well, this is both good and bad. NS support found the issue: A custom field on Subscription that sourced from a Price Plan saved search. That saved search used Subscription as the filter on Price Plan. Turns out, that’s terrible because it’s a field available on price plan, but not a stored field. It is itself a formula that pulls the subscription from the related subscription line. And given that we have over 123,000 price plans, every time we loaded a subscription record it had to run the equivalent of 123 thousand search/lookups within the larger saved search. They really should not make that field available on the saved search criteria and filters if using it is such a disaster. Some contractor we hired created that field and search, not realizing how bad it would be. The good news is we found the cause of the issue. The bad news is, it was caused by using standard functionality of Netsuite that just has terrible performance effects. I guess I’d say to everyone, beware the subscription field on price plan saved searches. Just don’t use it if you don’t need it.

wow thanks for following up with the root cause... glad you were able to figure it out