@kyle - I agree with @andy 's comment. I've previously worked with NetSuite before dealing with issues such as this and my general advice would be: SuiteCloud+ helps leverage volume processing issues of transactions or records in the system. A good example is before Groupon had to process at the min. 30k+ vendor bill payments a day through the Electronic Payments bundle of NetSuite - This caused some perf. issues. When they used SuiteCould+, the performance got better. Scheduled process scripts and other processes in the system as well as bulk processing of transactions are better managed through SuiteCloud+ because of the extra queues that the feature can provide to allow different processes to run in parallel. Using a higher service tier is usually advantageous especially when handling NetSuite version upgrades and db specific issues. One major concern that is raised by customers' under a shared db is when fixes or changes are introduced in the db which their accounts sit in - A fix for a specific account could sometimes have a different effect on other accounts within the same db considering the script customizations and workflows embedded in each account. However, there are perf. issues that are systemwide in NetSuite - That's something that can only be remedied by a fix from NetSuite. I guess the best move is to first assess the root cause of the perf. issues experienced then identify what available options can be done to resolve or mitigate the problem. An alternative site the provide in some instances could help like what @hasany has mentioned: system2.netsuite.com. For systemwide issues, you can go through this site to stay updated on the fixes or state of the site : https://status.netsuite.com/