Hi LP,
Definitions:
- Request a second - Number of request that can be made a second.
- Burst - Number of request we will allow to be queued before rejecting. The request in the queue are slowed down at the request a second rate.
v1.2
- Request a second - 8
- Burst - 40
2.0_rc+
- Request a second - 24
- Burst - 40
I would not multithread adding works per a researcher. Instead I would set the expectation that adding 300 works is an asynchronous process and can take a few minutes to complete. A messing such as "We are pushing your activities to your ORCID record, for researchers with large records this can take up to 10 minutes to synchronize"
The development team does have plans to have a batch post for activities (something like 50 at a time), however do to bandwidth issues we have not gotten to implementation yet.
Cheers,
Rob