surf_doggie said:
Im confused then how can the logs show 3 to 5 pages being grabbed at
the same time down to the second and it not be a concurrent connect?
Ive put cross section of a log below, am I missing something?
5/25/2006-----------------3:46:42 PM
http://www.jhdesigninc.com/Campaign-Items/Special-Campaign-Package.asp
Refering Web Address
Mozilla/4.0 (compatible; MSIE 6.0; Windows XP) Browser Type
C:\websites\websites\jhdesign\Campaign-Items\disclaimer.asp Page Viewed
63.148.99.237 Remote Address
5/25/2006-----------------3:46:42 PM
http://www.jhdesigninc.com/Campaign-Items/Election-Day-Polls.asp
Refering Web Address
Mozilla/4.0 (compatible; MSIE 6.0; Windows XP) Browser Type
C:\websites\websites\jhdesign\Campaign-Items\Poly-Sleeve-YardSigns.asp
Page Viewed
63.148.99.237 Remote Address
5/25/2006-----------------3:46:42 PM
http://www.jhdesigninc.com/Campaign-Items/Election-Day-Polls.asp
Refering Web Address
Mozilla/4.0 (compatible; MSIE 6.0; Windows XP) Browser Type
C:\websites\websites\jhdesign\Campaign-Items\Political-Posters.asp Page
Viewed
63.148.99.237 Remote Address
It appears to me that this bot has 3 concurent connections am I
incorrect in that assumption? The original question refers to refining
db connections. This site only has a 1 meg access db. I had a client
with a 60 meg site and once a week or so it would go down once I
changed them to mySql no worries. Later while checking the logs I
realized there was a lot of traffic hitting the access db I didnt know
about. As soon as I went to mySql it was smooth sailing.
Earl
www.jhdesigninc.com
That might be 3 concurrent connections - it might not. It depends on
what db interaction each page involves.
A typical SELECT of 14,000 rows from a db on my machine (XP Pro, IIS
5.1, 52Mb Ram - nothing special) might take 0.05 secs to execute from
instantiation of connection object to closing it again. So you can
have 20 separate connections per second serially using that example.
MS claim that Jet supports 225 concurrent users (connections), so
theoretically, you could perform my test operation 4,500 times a
second. But they also recommend that you do not use Jet where you may
exceed 10 concurrent users, so that's 200 times per second.
Threre is no doubt whatsoever that SQL Server is a far superior
solution than Jet, but it is highly unlikely that the SIZE of your
client's db was the problem. Inefficient use of connections, use of
ODBC, version of driver, weight of traffic are all more likely to be
contributors.
I had a site that "fell over" regularly using Access 97 and a system
DSN on 20,000 page impressions a month (5 db calls per page - db about
10Mb). I changed it to Access 2000, use the Jet 4 driver and it now
serves 5 times as much traffic on a db approaching 200Mb, and hasn't
had a problem in 3 years.
I've been trying to find out just how scalable Jet is in a web
environment, but there isn't very much information available. The
difficulty is that there are so many variables involved in scalability,
so I have found - but size of db isn't one of them. I bookmarked an
article I found a few years ago that suggested Jet should be
comfortable serving up 50,000 reads an hour, but I lost that together
with the PC I was using when the "magic smoke" escaped from it.