I wanted to respond to this thread, with some very interesting stuff I
have learned recently. The issue is, it is one of my longer type
posts, and includes some graphs from my zabbix monitoring system. So I
was planning to create a html page or something and link to it, but I
just haven't had time. But since I have posted the link now to
http://devcom.bighead.net/
I went ahead and posted on there, where it is very simple to format,
and add images and such. I think it is some valuable information
regarding this thread, and also dealing with persistant connections,
caching, and datasourcelife and the like.
Here is a direct link to the post.
http://devcom.bighead.net/showthread.php?t=20
Feel free to comment or add your own information.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Sep 15, 2008, at 11:03 AM, Robert Garcia wrote:
I have seen that, it happens during heavy traffic, and witango will
just keep loading up a DB. I can post more detail on this
information tonight, too busy now.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Sep 15, 2008, at 10:52 AM, Ted Wolfley wrote:
How did you get 200 connections? The most we get on one Witango
server at one time is 9.
Ted
From: Robert Shubert [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2008 12:43 PM
To: witango-talk@witango.com
Subject: RE: Witango-Talk: datasource timeout
A datasourcetimeout of 15-60 minutes is acceptable. All this means
is that during times of no/lower activity unused connections will
be closed to free up resources.
Each ODBC connection consumes memory (about ½ MB I think), today’s
servers have no problems juggling 10s or even 100s of them. As I
write this there are over 200 connections between my Witango
services and my SQL server. The nice thing is that if Witango needs
to ramp-up to 20-30 connections to service some peak traffic, most
of them will timeout during low traffic. Refreshing ODBC
connections can be healthy as well. Especially if you have a
problem with your SQL server or network, Witango will need to kill
off all active connections and make new ones.
For you second question, use @HTTPATTRIBUTE to look for these bots
at the top of your TAFs and send back a handmade 404 error.
Robert
From: Ted Wolfley [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2008 11:05 AM
To: witango-talk@witango.com
Subject: Witango-Talk: datasource timeout
Hi,
2 questions:
Question 1:
On our win2003 box running Witango 5.5, we noticed we have
DATASOURCELIFE=1440, a carry over from when we used to run
RTango2000 and Oterro ODBC. Has any one run into any problems
running the datasourcelife at its default of 30? Our website is
getting hit constantly by bots and wondering if lowering the
datasourcelife would increase proformance.
Queston 2:
Related to question 1, in the iis logs, there are a lot of entries
that have “lwp-trivial/1.41” or “LWP::Simple/5.805”. Does anyone
have a recommendation on how to handle them. They are hitting the
site about every 3 seconds.
Ted Wolfley
Lead Internet and Database Programmer
The Ogden Group of Rochester
phone: (585) 321 1060 x23
fax: (585) 321 0043
[EMAIL PROTECTED]
www.ogdengroup.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
