Hey Ian,
Thanks for the info! I've set the Access threads for 5 and reset the threadpoolsize back down and still got the same result. Looks like I'm going to have to put this site on another server! Best Regards, Rick > Hey Rick: > > Lots of DBMSs are faster than Access, but access should be fine under even > medium load (no flames, pls). > > It depends more on things that I know that you already know: > > -- only searching on indexed fields, > -- never doing a "contains" search; > -- etc. > > Two things that relate to the Witango-ODBC smooth operation: > > -- put that threadpool size back down to the default. Opening up more > Witango threads will not assist your cause, due to the nature of how Version > 4 is threaded; and > > -- go to your ODBC driver for your Access datasource and snoop around until > you find the number of threads that it opens. By default, it opens three > threads into Access. I have set this successfully up to ten threads without > incident. I typically set it to 5 threads. If you set it to 5 and you see > a performance improvement, you'll know that your bottleneck is the > datasource, and it will soon be time to change it to a more robust DBMS. > > -- another thing: ensure that your Access ODBC driver is for Access 2000 ... > not Access 97. Note: the database itself can still be Access 97, no > problem, but there was a large performance improvement made in the ODBC > interface for Access when they released Access 2000. The performance > improvement is in the range of 2-3 times. > > For others on the list, Access was designed as a single-user database, and > was never intended to allow the sort of loading that is possible from > multiple users via the 'net. However, by multi-plexing Witango threads with > Access datasource threads, you can do very well. If your database architect > is exceedingly intelligent in the use of query optimizing tactics, you can > quite literally get away with huge traffic on an Access site. > > cheers, > Ian > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Rick Sanders > Sent: Monday, August 12, 2002 9:24 AM > To: Multiple recipients of list witango-talk > Subject: Re: Witango-Talk: Resources > > Ian and John, > > Thanks for the quick reply! > > I've turned logging on and it seems that the site is really high-traffic. > The site is using access as the DB. Would changing it to PSQL or MSSQL help > the speed? The t4server.exe is at 99% in the task manager and stays there. > > Is there another solution besides putting the site on it's own dedicated > server? > > Thanks! > > Rick Sanders > President, Web Energy > Tel: (514) 620-3006 > Fax: (514) 620-3017 > Web: www.webenergy-sw.com > > ----- Original Message ----- > From: "Jon Grieve" <[EMAIL PROTECTED]> > To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> > Sent: Monday, August 12, 2002 12:05 PM > Subject: RE: Witango-Talk: Resources > > > Rick, > > > > Check the NT/2000 Task Manager (r/click the Taskbar) and examine the > > Processes tab. If you sort that by CPU/CPU Time, you can see 'who' is > > hogging the CPU(s). > > > > On my Win2K Server, I've seen both CPUs locked at 100% by Perl.exe. Perl > > was invoked by Tango, but the t4server process was idle. > > > > Jon > > > > -----Original Message----- > > From: Rick Sanders [mailto:[EMAIL PROTECTED]] > > Sent: 12 August 2002 4:59 > > To: Multiple recipients of list witango-talk > > Subject: Witango-Talk: Resources > > > > Hi List, > > > > Anyone ever have the Tango server use all the CPU resources (99%) under > > Windows and not release the resources? > > > > I'm wondering if I have a virus. I've uninstalled and re-installed the > Tango > > server. I set the threadpoolsize to 100 and I put caching on. > > > > Query timeout is set to 2 minutes, and it's set to disconnect the > > datasources immediately after use. > > > > Is it my machine, or is the load so high that I need a professional > version? > > > > Rick Sanders > > President, Web Energy > > Tel: (514) 620-3006 > > Fax: (514) 620-3017 > > Web: www.webenergy-sw.com > > ________________________________________________________________________ > > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > > with unsubscribe witango-talk in the message body > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
