SP load balancing

Cantor, Scott cantor.2 at osu.edu
Mon Sep 10 13:25:33 EDT 2012


On 9/10/12 1:13 PM, "Paul Brears" <pbrears at rm.com> wrote:

>The SP documentation has recommendations for using persistence where
>required or the shared Shibd/ODBC solutions where session persistence
>isn¹t not practical.
> 
>Are there any plans to offer using cookies on the SP to hold enough
>session state to eliminate the need for either a shared store of sessions
>or load balancing persistence?

In the abstract, it's impossible because the data size is unbounded.

In practical terms, yes, I've considered it. I should probably add it to
the roadmap given that it's a large amount of work.

My guess is that it would not perform particularly well but would solve
the stickyness problem associated with deployments that wanted to keep the
session around only for the purpose of supporting logout or something like
that. All the sessioning I know of in application frameworks that support
arbitrary data objects use server-side sessions for performance.

It hasn't seemed compelling to do it if it doesn't work for full-on use
across all the requests. Of course since I don't actually know that it
*wouldn't* perform well enough to use on a typical web app with dozens of
requests to the server each page, I'm speculating. If it did, that would
be a more compelling case for it.

-- Scott




More information about the users mailing list