SuiteCloud Processors Processor Allotment Per Account
SuiteCloud Processors are used to execute (process) all scheduled script and map/reduce script instances. However, this topic does not apply to scheduled script deployments that continue to use queues. See SuiteCloud Plus Settings for more information.
SuiteCloud Processor Allotment
|
Service Tier |
Maximum SuiteCloud Plus Licenses |
Maximum SuiteCloud Processors |
|---|---|---|
|
Standard |
1 |
5 |
|
Premium |
3 |
15 |
|
Enterprise |
6 |
30 |
|
Ultimate |
12 |
60 |
*The default number of SuiteCloud Processors available is 2 if you have not purchased any SuiteCloud Plus licenses.
For more information, see SuiteCloud Plus Settings and NetSuite Service Tiers.
Accounts Without a SuiteCloud Plus License
Accounts without a SuiteCloud Plus license now have access to two processors. The extra processor doubles the processing bandwidth for scheduled scripts and map/ reduce scripts.
If any of your scripts depend on implicit dependencies imposed by having one processor, you may be required to update your existing scripts for this feature. When an account has access to only one processor, all jobs are processed one at a time. If all jobs have the same priority, the order of processing is always first in, first out. Some scripts may depend on this behavior. With the addition of an extra processor, these scripts may no longer process in the correct order.
For example, if you have a script that pre-processes data for a second script, the first script must complete execution before the second script begins. With one processor, you can submit the scripts in the appropriate order and know that the order of processing is as expected. With two processors, there is a possibility that the second script submitted starts execution before the first script completes.
To handle the above scenario, perform the following steps:
-
Review your scheduled and map/reduce scripts to find scripts that depend on a specific order of execution.
-
Use the following SuiteScript APIs within the first script to programmatically submit the dependent script. This action ensures that the scripts are always executed in the correct order.
-
For a scheduled script, call task.ScheduledScriptTask and place the code at the end of the script.
-
For a map/reduce script, call task.MapReduceScriptTask and place the code at the end of the summarize stage.
-