Cxense R&D have decided to start enforcing the rate limiting for /document/update API calls.
Rate limiting is documented on our Wiki, at this url: https://wiki.cxense.com/
display/cust/Error+codes+and+ responses, but we have not implemented it for this API until now.
Feeding clients will receive a response in the shape of "429 Too many requests"-errors whenever they are feeding at a too high rate. Customers will have to change their implementation of their feeding clients in order to retry the documents that fails.
The reason for this, is that our operations team have been observing feeding lag when customers feed faster than ~100kB/s. The limit is put in place to prevent the lag, and to divide our capacity more evenly across all customers. The actual limit will be tailored to tune the performance of the backend. It may be lower than 100kB/s.