anyone else having performance issues with csv imports running really slow after OCI upgrade? We have some scheduled csv uploads that used to take about 1-2 hours to process. They are now taking over 8 hours even with multi threading on and the run server scripts checkbox unchecked. It's not isolated to a specific csv import or record either, happens with adhoc uploads and with records such as: items, sales orders, purchase orders, custom records

my experience is during recent upgrades (versioning or OCI) seems like the threads in the same tenant divert to upgrading rather than running - in some instances i've seen even if you have more than one suitecloud processors, you can have MR scripts queued but not running but I cant confirm/quantify if that the quality of service has gone down overall

Sorry for the late reply, but maybe this will help. I had this issue after we were migrated to OCI last year. Imports that we ran for years and ran 20-25 mins like clockwork were suddenly taking 2X+ the time (50+ minutes). We complained about it and made a business case that the performance degradation was causing issues maintaining pricing (and other functionalities) as quick as we were previously, and that it presented a financial burden. After much protest about the performance, they eventually moved us to a different host within the OCI datacenter and performance improved (back to what we expected).

@Dan Curtis appreciate your response, that insight definitely helps. We are seeing a minimum of 2X+ different as well and one of our issues revolves around pricing updates as well. Have a call with NS this week to discuss further. And thanks for that insight about being able to move to a different host within the data center ill see if that's a viable option.

Good luck! I know once we found some resolution from NS, we also looked at other ways to reduce our pricing CSV imports. One thing we found: If we exported 10k skus to update, we'd update our pricing in Excel/GSheet and reimport the list of 10k to perform the update. Now we take a few extra seconds to check WHICH rows are actually changing and getting updated. If only 2k skus out of 10k on the list changed, we ONLY import the 2k rows that changed. Essentially only importing the incremental changes, rather than the entire sheet. This trimmed our CSV processing time down and has become a new standard for us. "If the price didn't change, there's no reason to import that record." Granted, it's not uncommon for all 10k skus to be affected, so in that case we import all records. But helped us trim some of the "fat" of the import time out. Hope this helps.