Does concurrency limit on an integration take away from the pool shared with other integrations?

AI generated answer (using internal Slack threads):

Based on the conversations, the concurrency limit on an integration does not take away from the pool shared with other integrations. Instead, it sets a limit that a particular script cannot exceed. This limit is shared among all scripts at the account level, and is determined by factors such as the service tier and SuiteCloud+ licenses. In the context of NetSuite, concurrency refers to the number of simultaneous processes that can be run. If you have a concurrency limit of 15, and you have 3 scripts each with a concurrency limit of 10, and they all get queued at similar times, one of the jobs is likely to take 10 lanes, and 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. The advantage of setting a concurrency limit below your provisioned number of processors is that it prevents long-running processes from monopolizing all of the processors, allowing other jobs to run. However, if you want to maintain the order of operations, you might lower the concurrency on a job. For Suitelets, the governance limit for concurrent requests for Suitelets available without login is the same as the limit for RESTlets. For Suitelets that are authenticated through login, the number of concurrent requests is currently not governed. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******