|
|
|
|
|
by Hilift
225 days ago
|
|
Multiple Active Result Sets (MARS). During large query responses or bulk loads, "full" packets cause an additional packet to be sent over the wire with about five bytes to hold the MARS "wrapper". The net result is one full packet, and one empty packet on the wire, alternating. The performance impact in LAN latency is negligible. However on higher latency between AWS and your premises it has a terrible performance impact. MARS isn't strictly needed for most things. Some features that requires it are ORM (EF) proxies and lazy loading. If you need MARS, there are third party "accelerators" that workaround this madness. "MARS Acceleration significantly improves the performance of connections that use the Multiple Active Result Sets (MARS) connection option." https://documentation.nitrosphere.com/resources/release-note... |
|
I use and love EF, but generally leave MARS off when possible because it is responsible for more trouble than performance gains nearly every time.