NetAsset - Optimize for High Volume
Overview
If you have a high volume of assets in NetGain products, especially NetAsset, you may notice longer processing times. This article explains how to optimize system performance, including script priorities, concurrency limits, and strategies for scheduling, along with estimated processing times.
Understanding Netgain Performance
Netgain products are fully embedded in NetSuite, meaning all processing relies on NetSuite servers and capabilities.
Scripts are designed for efficiency. There are no modifications available to the scripts themselves that will significantly increase processing speed. Optimization is achieved by configuring NetSuite resources and scheduling processes strategically.
Key Configuration Options
1. Script Concurrency Limit
Definition: Determines how many queues are available for multi-threaded processing in NetSuite.
Default: Unlimited (uses all available queues).
When to Adjust:
If other processes in your system need priority, consider lowering concurrency to avoid queue conflicts.
If speed is the top priority, concurrency can remain unlimited (if licenses allow).
How to Check and Update Concurrency Limits:
Go to Customization > Scripting > Scripts.
Edit the desired Map/Reduce script.
Adjust the Concurrency Limit field based on your needs.
2. Script Priority
Definition: Determines the priority of Map/Reduce scripts in the NetSuite queue. Options: Low, Standard, High.
Default: Standard
When to Adjust:
If other scripts are competing for queues, leave it at Standard to avoid interruptions.
To prevent other scripts from throttling processing power, set priority to High.
How to Update Script Priority:
Use the product setup page in the Netgain Product to update the Default Script Priority.
3. SuiteCloud Plus Licenses
Purpose: Adds additional processing queues for multi-threaded scripts, which is critical for large NetAsset jobs.
Availability: Most accounts start with 2 queues; SuiteCloud Plus Licenses add more. See more on Oracles NetSuite Help Documents.
When to Purchase:
< 10,000 assets: Not necessary, but would increase processing speeds if desired.
10,000–30,000 assets: Recommended
> 30,000 assets: Needed for reasonable performance
Note: Licenses must be purchased permanently; temporary purchases are not available.
4. Scheduling & Timing Strategies
Run heavy processes (schedules, journals, reports) during off-peak hours.
Consider batching uploads in stages (e.g., 25,000 assets per upload).
Estimated Processing Times
We have put together a schedule and journal processing time calculator that can be used to estimate the average time it will take to run those scripts based on the number of assets. Note that these are just estimates, and actual processing times will largely vary based on the factors below.
NetAsset/NetLease Processing Times Calculator
Factors affecting performance:
Useful life of assets
Number of available queues
Other scripts running concurrently
Best Practices
Plan for longer timelines: Schedule generation and uploads may take multiple days to weeks for higher volumes.
Limit concurrent processes: Reduce queue competition during NetAsset processing.
Check script deployment carefully:
If processing severely impacts other tasks, temporarily undeploy scripts:
Customization > Scripting > Map/Reduce Script Status
Uncheck the Deployed checkbox for NetAsset scripts
After clearing queues, redeploy scripts
Monitor processing metrics: Check Script Status and queue utilization to identify bottlenecks.
