For one search action, anything less 100ms and I generally leave it be. But at 500ms or more I'm pulling (what little is left of) my hair out trying to fix the issue, as it is a real drain on performance, and has a negative impact on the user's (and client's) perception of the application I've built.
Very long lists, very large results sets, and aggregated reports may take more than 500ms. Everything else, I try to get below that 100ms threshold. I generally find that when the SQL/DBMS are optimised, the rest just falls into place. If the same SQL is running against the same DBMS but takes 500+ms in Witango and is almost free in .NET, then I would suspect that .NET is doing results caching. On Tue, Oct 6, 2009 at 10:54 AM, Ted Wolfley <[email protected]> wrote: > Witango speed stayed about the same on repeat queries and the > datsourcelife is set at the default. > > The ajax taf is tiny and using the Direct_DBMS for the query via a tcf. > The database connection is opened at login to the site. > > > > I guess we will go with the .NET version until we see what Witango 6 has to > offer. > > > > Thanks > > > > Ted > > > ------------------------------ > > *From:* Robert Garcia [mailto:[email protected]] > *Sent:* Tuesday, October 06, 2009 10:12 AM > > *To:* [email protected] > *Subject:* Re: Witango-Talk: autocomplete speed comparison > > > > ODBC and persistent connections would be my guess, as long as ALL OTHER > variables are equal. Repeat the query a few times, and see if it is faster. > Witango is most likely using ODBC connector and .NET is using a more native, > optimized connection. Witango will always take longer on its FIRST query to > a connection, due to the overhead of opening a connection from scratch. > Witango will then hold that connection in memory and try to reuse it, saving > time on subsequent queries. This seems efficient, but it actually ends up > wasting memory on both the witango side and especially the db server side. > > > > Check the documentation on the datasourcelife configuration variable. > > > > -- > > > > 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 Oct 6, 2009, at 6:44 AM, Ted Wolfley wrote: > > > > Hi, > > > > We created a simple ajax autocomplete retrieving name and company from a > sql server 2005 table on another server. We compared 2 different options. > > > > Both servers are Windows 2003 32-bit > > > > Using Witango 5.5, the query request took 528ms. > > Using ASP.Net, the query request took 34 ms > > > > The sql statement is the same for both queries > > > > Wondering if someone could give an explanation why there is so much > difference in speed and is there a way to speed up the Witango query. > > > > 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
