Are there published expected speeds (ie 5 records ...
# suitetalkapi
r
Are there published expected speeds (ie 5 records per second, etc) for the SOAP connection? I thought there were, but I've dug through a bunch of documentation and haven't been able to find anything. 6 per second is sticking in my mind, but that might be for CSV.
s
It depends on how many concurrent threads you have with netsuite, it's really up to you how many you want to burn per app. If you go over the request will fail with an appropriate error code
r
it's really up to you how many you want to burn per app
This may be a dumb question, but we do have some SC+ licenses. From what I can tell, the threads/processors seem to be only for scripts, but can we use those to redirect a bunch of horsepower to the SOAP integrations? We're still testing in Sandbox, but the speeds seem excessively slow, only about 20 records per minute.
We don't have much for scripting in the system, so if we could redirect some of the processing power that's slotted for scripting to the SOAP connections, that would be ideal. I'm not sure if that's possible or how to do it.
s
I believe threads are ubiquitous between scripts and SOAP. Sandbox should always be slower than prod, sandbox instances are generally shared between many orgas per machine
Can also see what you have and how you use it in customization -> performance -> concurrency monitor
b
suitecould plus increases concurrency for your account
doesnt increase the speed, though you will be able to process more records at the same time
for soap based integrations, that generally requires support from your integrator
a
Piggybacking on this thread: is there a way to programmatically read what is the configured concurrency on an instance?
b
a
Cool! is there an equivalent for REST?
b
no
a
do you know if the concurrency limit is shared? as in, if the SOAP endpoint returns 30 threads, does that mean that the REST can also have 30 threads concurrently? Doesn’t seem like there are two separate concurrency values configured