Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Aug 02, 2012 04:23 AM by gnoix
Jun 01, 2012 06:59 AM|LINK
Just want to ask if there's a best #s of limits in ASP > Session Properties in IIS7. I know in IIS6 we can based in the number of CPUs and stuff. Right now the defaults are below, plase advise if this is ok to be left
as is thought the max session limit seems to be really high: 4294967295
Maximum Sessions: 4294967295
Time-out: 20 (mins)
Also on the Web Site > Advance Properties > Connection Limits.
What would be the best #s of limit can be set i.e. for number of CPUs 2 or 4? below are the Defaul settings, please advise what would be the appropriate limits, this seems to be really high.
Connection time-out: 600
Maximum Bandwidth: 4294967295
Maximum Concorrent Sessions: 4294967295
Aug 01, 2012 07:06 AM|LINK
Hi, I had similiar concerns before, and it was very difficult for me to find optimal values with very good reasons to limit.
In most case, I think the values are as high as possible, because end-users doesn't want to see errors because of my settings.
Otherwise, I should prepare perfect reasons to explain the reasons why they should meet the errors, very well.
In terms of session peroperties, high values can be a concern for worker process memory(w3wp), can be shown in a task manager(Virtual Memory Size). If it's stable enough, much lesser than 2GB, or 1GB, & never causes OOM(out-of-memory), you can leave them
default. otherwise, it's better to follow troubleshooting instructions for memory leak issues of web applications.
In terms of connection time-out, you adjusted a default value which is 120 seconds to 600. I think it's reasonable as long as it's between 2 minutes & 15 minutes(A default value of IIS5). Browsers also have connection time-out, so shorter one will be applied,
and connections are being closed by browsers anyway. (I remember it's around 100 seconds, not sure). if you set this shorter than 100, there can be other concerns, such as connections need to be reestablished more frequently, which can be overhead of CPU.
In terms of bandwidth, this can be useful when your IIS hosts multiple web sites, and you don't want to allow a single site to occupy whole network bandwidth. Web Hosting companies condier using this because each site for each customer, pay same cost for
running their sites, never wants to be bothered by others sites. So, you can limit bandwidth for every sites to share bandwidth fairly, by limiting maximum bandwidth for each site. otherwise, you dont' need to limit bandwidth.
hope this helps.
Aug 02, 2012 04:23 AM|LINK
there will be no exact answer for this.
the best session timed out and connection limit is depended on your requirements, considering the working time on site you need and the security reason will be a concern in setting these session and connection limit value.