Is Cold Fusion REALLY multi threaded?

Yes, ColdFusion Server is multithreaded;  AFAIK, CF does not simply call one DB call at a time, that would be utterly ridiculous and a waste of time! What are your servers specs?  Memory etc..?   Neil Please, someone tell me that there is a configuration option I have wrong. If I execute a killer query (one that takes, say 2 mins for the database to return the result set) from a coldfusion page, then all other cold fusion users are left hanging until the query has returned it's result set.. If, however, I execute the same query from the database client, it still takes the same amount of time to return the result set, but has no discernable effect on the response times of the coldfusion users. This suggests to me that CF only executes one DB query at a time - please tell me I'm wrong.  This also explains why our system response times are so lame when there are more than about 20 people on line For the record, the applicable CF Admin settings ara: - Single Threading: not checked - Variable Scope Lock settings:  all set to no automatic checking or locking Is there anything else I need to set? Environment: Op Sys: linux Red Hat Linux 2.4.2 CF v5.0 Unix ODBC Postgres 7.2.3 database ----------------------------- Stephen Richards 020 7903 3226 ------------------------------

Another thing to check, in Select queries are you using the Blockfactor = x (x being a number between 1 and 100).  Using Blockfactor causes CF to bring back blocks of results. Mike Brunt - CTO Webapper Services LLC Blog - http://www.webapper.net Downey CA Office 562.243.6255 AIM webappermb Web Application Specialists [mailto:Neil.Robertson-Ravo@csd.reedexpo.com] Sent: Thursday, December 05, 2002 2:26 AM To: CF-Talk Subject: RE: Is Cold Fusion REALLY multi threaded? Yes, ColdFusion Server is multithreaded;  AFAIK, CF does not simply call one DB call at a time, that would be utterly ridiculous and a waste of time! What are your servers specs?  Memory etc..? Neil Please, someone tell me that there is a configuration option I have wrong. If I execute a killer query (one that takes, say 2 mins for the database to return the result set) from a coldfusion page, then all other cold fusion users are left hanging until the query has returned it's result set.. If, however, I execute the same query from the database client, it still takes the same amount of time to return the result set, but has no discernable effect on the response times of the coldfusion users. This suggests to me that CF only executes one DB query at a time - please tell me I'm wrong.  This also explains why our system response times are so lame when there are more than about 20 people on line For the record, the applicable CF Admin settings ara: - Single Threading: not checked - Variable Scope Lock settings:  all set to no automatic checking or locking Is there anything else I need to set? Environment: Op Sys: linux Red Hat Linux 2.4.2 CF v5.0 Unix ODBC Postgres 7.2.3 database ----------------------------- Stephen Richards 020 7903 3226 ------------------------------

Stephen Richards wrote: > > For the record, the applicable CF Admin settings ara: > - Single Threading: not checked > - Variable Scope Lock settings:  all set to no automatic checking or locking > > Is there anything else I need to set? For the datasource, what do you have for "Limit simultaneous connections" and what is your CF setting for simultaneous requests? Jochem

Stephen Richards wrote: > > Limit connections is not checked, however the value is 0. OK, next step is to check the number of database connections you actually have. Easiest is if you are only using one datasource on that particular server, just run a netstat and check the number of TCP connections to port 5423. Else, start working from the database side, use the standard tools to determine the number of backends and their status. Alsomake sure you are not running with a default transaction level of serializable, which would make all transactions run pretty much after eachother. Jochem

> Subject: Is Cold Fusion REALLY multi threaded? Yes, it really is. ----- Excess quoted text cut - see Original Post for more ----- This may be a problem with your specific database drivers. I'm not especially familiar with PostgreSQL, but I've seen similar things in the (relatively distant) past with Oracle ODBC drivers - they were essentially single-threaded, so all queries were queued - which, as you've discovered, is very bad for performance! Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444