|
I have 2 thoughts on this issue. 1) User scopes don’t really do much harm, and use very little
memory. Under Witango (5.0-5.5) I have had 10,000+ user variables established
on my server without a problem. I use a 60 minute default timeout now (and my
clients to often increase that), so it’s not unusual for me to see
2,000-3,000 user sessions during the typical business afternoon and I rarely
drop below 1,000. There doesn’t seem to be any harm in any of this, so I
would just let the server do its job. 2) You do have the ability to identify what is accessing your system.
For example, you can use the user-agent to identify search engines – I’m
sure there’s a list of them out there someplace – and you can
either set your user$variabletimeout to 1 or simply purge your user scope at
the end of your TAF when you identify a search engine as a user. Either way,
you can add this logic to a header/footer and it should clean up after you’ve
been crawled. Robert From: Fogelson, Steve
[mailto:[EMAIL PROTECTED] Andre Rekhtine’s post a couple of weeks ago
and some activity on one of my sights last night brought this to a head for me. I had a sight last night that SearchPublisher 3.0
was indexing. I am sure they are similar to other search engines in that each
request invokes a new user session. Imagine if you have 15 to 20 sites on a
Witango server, the normal 30 minute session inactivity variable purge, normal
traffic for each site and a few search engines start indexing the sites. User
sessions can exceed the 200 sessions that Andre talked about real quick. Are any of you addressing this and if so how? I was thinking about building a table to keep track
of user sessions that would maintain last access and number of accesses by user
reference. Then having a cron job run every minute to find sessions with only
one access for the last five minutes. The cron job would then purge the
inactive sessions. I am not even sure I can do this as I can’t find a tag
to purge other sessions users vars! I keep my user vars low – 4 or 5 per session
and I also realize that I could reduce the VARIABLETIMEOUT system setting, but
there are a lot of valid user sessions that I prefer not to keep requiring a
new session initialization. Comments please. Thanks Steve Fogelson Internet Commerce Solutions ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
- Witango-Talk: Search Engines & User sessions Fogelson, Steve
- RE: Witango-Talk: Search Engines & User sessions Robert Shubert
- Re: Witango-Talk: Search Engines & User sessions Robert Garcia
- Re: Witango-Talk: Search Engines & User sessions peter
