RAMSession thread safe?
To improve performance, I'd like to use a single RAMSession object across multiple threads. This is for strictly for read-only queries. Any concerns with this approach?
Note that I'm not looking for an absolute declaration of thread safety here. But a reply in the form of "well I've been doing it without problems for the past 6 months" or "the system was designed to work that way", that'd be helpful by itself.
Thanks!
Bas.
Note that I'm not looking for an absolute declaration of thread safety here. But a reply in the form of "well I've been doing it without problems for the past 6 months" or "the system was designed to work that way", that'd be helpful by itself.
Thanks!
Bas.
2 answers
I do not think you will have problems performing read only actions on the RAM API in multiple threads. We did intend for it to be used this way. Internally as well as other partners and customers have used it this way with no know issues.
However, we do not have a full regression suite in place, so we cannot claim official support for this use case.
However, we do not have a full regression suite in place, so we cannot claim official support for this use case.
To improve performance, I'd like to use a single RAMSession object across multiple threads. This is for strictly for read-only queries. Any concerns with this approach?
Note that I'm not looking for an absolute declaration of thread safety here. But a reply in the form of "well I've been doing it without problems for the past 6 months" or "the system was designed to work that way", that'd be helpful by itself.
Thanks!
Bas.
I do not think you will have problems performing read only actions on the RAM API in multiple threads. We did intend for it to be used this way. Internally as well as other partners and customers have used it this way with no know issues.
However, we do not have a full regression suite in place, so we cannot claim official support for this use case.
Thanks for the prompt reply Kevin, much appreciated!