I am being asked to extend the timeout duration of a asp.net Web App's session state. We are using InProc. We do not have a large user base and I understand all the arguments for and against the increase, but my question is this, what metrics can I monitor to asses the impacts of the increase and hopefully determine we can go longer, or determine that perhaps we have gone too far?
- How to determine 32 bit vs. 64 bit ASP.NET being used?
- Best way to encapsulate component that includes logic and webforms
- Updating numerous web clients periodically from the server
- how to make an web application in demo in our comapny web site
- open link in new tab for the imagebutton in asp.net
- How do I print an ASP clientID in a web page?
- Add attachements and pictures on ASP.NET
- handling events of controls added during runtime
- Invalid post back when button type is Button in datapager
- ASP.NET [Date Input]
- Dropdownlist Selected value is not working
- Should I cache instances of frequently accessed classes
- DLL problem (COM)
- How to create multiple preprocessor constants in ASP.NET Page Directive?
- How do I figure out which ASP control is throwing an exception?
- PL\SQL XMLTable performance
- Can't change log level at runtime (log4j2)
- how to generate random string for primary key in database table
- Fastest way to check intersection between a Rectangle List and a single Rectangle
- CGImageCreate: invalid image size: 0 x 0
- Partially applied generic function "cannot be cast to Nothing"
- how to add processing instruction in xml using XmlDocument
- Peek and Pop not an option
- RTSP Client Connected to VLC
- Get nodes of specific type in Networkx