Rick, Thanks for your quick response. That's what I was suspecting. Yes, we are doing everything in the worst possible way. This application was written several years ago for what was, back then, a small shipping system. Since we have grown in that timeframe from 400 people to over 1000 and the system has been expanded to cover all shipping and additional functionality it's degrading into almost total uselessness. I'm going to try coding some of the larger queries into stored procedures and using direct DBMS calls to see if this helps. You also have a good idea of bringing much of the data into an array and filtering the contents instead of calling another query. This is something I had not thought of and my be able to be used as well.
________________________________ From: Rick Sanders [mailto:[EMAIL PROTECTED] Sent: Thursday, June 28, 2007 9:05 AM To: [email protected] Subject: RE: Witango-Talk: Very puzzling... In my experience with WiTango loops, it's the application that's badly written. When returning a lot of records from the SQL database in a loop, it can take a really long time to display the results. I've tested queries and ran them directly on the database returning as many records, and it took a fraction of the time. ODBC has gotten better over the years, but it's still not as fast as connecting natively to the SQL engine. I've also done tests with the same function and query in Cold Fusion & ASP.net, and it was at least 25 times faster than WiTango. In some cases using the DirectDBMS action instead of a Search action has given me better performance. I've even gone as far as dumping the results to an excel file and displaying that back in the browser which was also quicker. I'd look at the queries, and see if there's a way to further limit the search results. Also, are you dumping the results to an array, then filtering or parsing the results? Rick Sanders President 902-401-7689 www.webenergy-sw.com Shop online for computer systems, accessories, and much, much more! http://shop.webenergy-sw.com <http://shop.webenergy-sw.com/> From: Wolf, Gene [mailto:[EMAIL PROTECTED] Sent: June 28, 2007 9:50 AM To: [email protected] Subject: Witango-Talk: Very puzzling... I have a situation here that I find very puzzling. So I am going back to the experts for advice. We have a few applications that, by their nature, perform thousands of requests against a SQL database and return thousands of records. I am quite sure that the coding of the application isn't as good as it could be and we will look into rewriting it. Here's our issue: This program, from start to the time it displays the returning page will take about 3 minutes. (stop groaning). We are testing this same application on a new box containing 8 dual core cpu's. I would expect one of those cpus to be pegged while Witango rips through these thousands of requests. Just the opposite. The cpus indicate hardly anything happening on the box. The same is true of SQL server. Even though I am literally throwing thousands of requests at SQL 2005 I'm seeing virtually no cpu activity on that box either. It looks almost like Witango is waiting for something, processes a request, waits a bit more, processes the next request, waits again, etc. The environment is Windows Server 2003. One Box is running Witango 5.5 with 8 dual core processors and the other box is Windows Server 2003 running SQL Server 2005. Yes, this program is coded and does some looping but I would still expect it to run one heck of a lot faster than it is. Any suggestions? Gene Wolf Supervisor, Business Systems DRS Sensors & Targeting Systems-Optronics 2330 Commerce Park Drive NE Palm Bay, Florida 32905 Phone: 321-309-0685 321-309-0202 (fax) Dictionary.com Word of the Day http://dictionary.reference.com/wordoftheday/ <http://dictionary.reference.com/wordoftheday/> This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior written approval from the U.S. Department of State." ________________________________________________________________________ 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
<<attachment: image003.jpg>>
