SuiteCloud Processors support two types of Suites Script 2.x tasks: Map/Reduce Script Type and Scheduled Script Type. These processors manage the execution of these scripts by allocating resources and handling prioritization to ensure efficient script processing. They are designed to enhance the performance and scalability of script deployments within NetSuite.
Impact on Map/Reduce Deployments
Concurrency Limit and Priority Settings
In map/reduce script deployments, the SuiteCloud Processors introduce a Concurrency Limit field, replacing the Queues field for accounts with SuiteCloud Plus. This field determines the maximum number of processors available for the deployment, equating to the number of jobs submitted for the map and reduce stages. For deployments created before the introduction of SuiteCloud Processors, the Concurrency Limit defaults to the number of options previously selected in the Queues field. If the Queues field had values 1, 3, 7, and 9 selected, the Concurrency Limit is set to 4. If Select All is enabled, the Concurrency Limit is left empty, allowing the total number of processors in the pool to determine the number of jobs created initially.
Priority Levels for Processing
All map/reduce script deployments include a Priority field, which SuiteCloud Processors use to determine the order of job processing. The available priority levels are High, Standard, and Low. High-priority jobs are processed first, followed by Standard, and then Low-priority jobs. The scheduler processes jobs of the same priority based on their submission time. By default, jobs are assigned a Standard priority but can be changed on the deployment record or the SuiteCloud Processors Priority Settings Page.
Impact on Scheduled Script Deployments
Removal of Queues and Priority Handling
Scheduled script deployments created after the introduction of SuiteCloud Processors do not use the Queue field. For deployments created before this update, the Queue field remains by default, allowing for FIFO (First In, First Out) processing orders within individual queues. However, all jobs, whether they use queues or not, are processed by the same common processor pool. Users have the option to remove the Queue field, and once removed, it cannot be reinstated. All scheduled script deployments also include a Priority field to determine processing order, similar to map/reduce script deployments.
Managing Legacy Queue Dependencies
For accounts with legacy dependencies on queue-based processing, the Queue field remains available to ensure continuity. This accommodation ensures that scripts relying on specific queue orders are not disrupted. Despite this, the overall processing is managed by a common algorithm, and all jobs compete for processor resources within the same pool, adhering to the priority and submission time rules.
By understanding these changes and utilizing the SuiteCloud Processors effectively, users can optimize their script deployment performance and resource management in NetSuite.