Whether you are using the ServiceAPI or your own web service built on the .Net SDK there a re a couple of things you can do to improve performance.
The object cache allows you to cache Records (and other objects) in memory, this removes the requirements to connect to the database next time this object is requested. This, is of course, most useful when certain Records are requested more than once. You can increase this to up to 99,999 for server applications (see below).
Workgroup Server Document Cache
When downloading a document it first must be fetched from the document store. The streaming technique used means this should be fast enough but if not you can choose to cache the documents on the workgroup server itself, so if you run a workgroup server on the same machine as you host your web service the documents will be available locally and the web service will not request them from the document store. Configure document caching in Enterprise Studio (see below).
Making this happen in your web service
To use the server object cache make sure you have called SetAsWebService, like this:
To fetch documents from the workgroup server cache:
- configure the cache,
- call SetAsWebService
- get the file location using the Record property DocumentPathInWGSCache