This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Can Lightspeed be used with multiple active result sets (MARS) to increase performance? Are there any cons in using it? |
|
|
|
|
No, LightSpeed does not support MARS.
|
|
|
|
|
We use Lightspeed 3.11, a SQL 2008 server for a MVC based website. Our solution has been working properly but when the workload increase on the site we are getting various casting errors for the entities in our views and the problems increase in frequency until the site is unusable. With MARS enabled these problems don’t seem to occur. Do you recognize anything about casting errors? Are the common and do you know about any other possible solution? What kind of negative effects could we expect if we enable MARS with Lightspeed? What kind of side effect do we risk? Is it possible to get documentation for older versions of Lightspeed? |
|
|
|
|
Do you have a stack trace from where you are seeing the casting errors occur? Typically this would be from a mismatch between the expected type on an entity property and the type of the actual value we are getting back from the database, or if you are using a composite key but we are expecting a primitive type or vice versa. Also how is your UnitOfWork scoping set up, do you have any concurrency (multiple threads) in accessing the UnitOfWork? I don't expect you would see any benefit or negative impact of enabling MARS as we don't specifically use it and are not expecting to use it so we only ever deal with single concurrent readers within a UnitOfWork. If you have a situation though where you have concurrent queries due to multiple threads against a single UnitOfWork that might explain while you are seeing a benefit but keep in mind that a UnitOfWork is not thread safe and should be only accessed by a single thread at a time.
|
|
|
|
