Cache persistence on domain name

Yes, the default persist time is 180 seconds, however, if you notice in the second rule I actually set this to an hour. Yes, it does have the potential to create a lot of persist records, but they are fairly small and the system can support millions of them with no effect on performance.

 

 

Yes, the drawback to using regular persistence is that when the persist entry times out (due to lack of usage), then the new request will get load balanced to a new member. However, one of the side benefits to HASH persistence is that it even if there is no persist record, it will still persist to the member that is a result of taking the number of active pool member modulo the hash value. So, this should help keep the requests going to the same member even though the persist entry timed out. (I actually forgot about this last night and hence I don't think increasing the persist timeout value is necessary).

 

 

Lastly, yes you could just set the request directly to the member and not worry about it, however, persistence already takes care of that so why bother? (I guess if you wanted to simulate the hash persistence behavior above, you could certainly do that).