Hello Olivier,
Where exactly did you read this? I would say that it is recommend to use
as less objects as possible that are larger than 83KB because these will
be created in the large object heap but this is always true and has nothing
to do with persisting the session state in a SQL Server.
Also when you serializer/deserialize large datasets for example there are
lot of short lived memory allocations which puts the .NET memory manager
under a lot of stressbut then again this is always true when serializing/deserializing
datasets whether or not they are larger than 83KB.
Can you point me to an article where you've read about not exceeding 80KB
per user for session state?
Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net
Does someone know why Microsoft advises not to exceed 80ko per user
for the asp sessions when they are stored in a SQL SERVER