what is the difference between concurruncy limit and biffer size in map reduce script?

AI generated answer (using internal Slack threads):

In NetSuite's Map/Reduce scripts, Concurrency Limit and Buffer Size are two different parameters that control how the script is executed. Concurrency Limit is a parameter that you can set at the deployment level of a Map/Reduce script. It determines the number of parallel threads that can be used by the script. The concurrency limit is shared at the account level based on factors like Tier, SuiteCloud+ licenses. If you have multiple scripts with concurrency limits and they all get queued at similar times, they will share the available processors. For example, if you have 15 processors and 3 scripts with 10 concurrency limits, one of the jobs might take 10 lanes, the other will take 5 until one of the first two jobs are done, then they will do the same split again until the jobs are finished. Lowering a concurrency limit below your provisioned number of processors can prevent long running processes from hogging all of the processors so that other jobs can run. Buffer Size is not mentioned in the provided threads, but in general, it refers to the amount of data that can be held in memory before it is processed. In the context of Map/Reduce scripts, this could refer to the amount of data that is processed in each map or reduce stage. It's important to note that setting the Concurrency Limit to 1 in a Map/Reduce script effectively processes the results sequentially, one at a time. This can be useful in certain scenarios where concurrent calls are causing issues. However, even with concurrency set to 1, you get the two-stage processing, automatic yielding, the sort/shuffle logic, and unlimited governance to do what needs doing in a Map/Reduce script. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******