I suggest you update to the latest version of WT if you are going to use objects in high scopes. There have been improvements made to better support their usage under load. Also note that while this is a performance boost, you will need to work up some routines to properly recreate the object when you update it, simply purging the TCF file wont be enough.
Robert _____ From: Robert Garcia [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 11:25 AM To: [email protected] Subject: Re: Witango-Talk: performance question Its actually better practice, to use instance events, with the object being a domain var, and methods in the TCF to get and set, but its up to you. -- 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 Feb 25, 2008, at 8:32 AM, Ted Wolfley wrote: Thanks, Ill give it a try. Ted _____ From: Robert Garcia [ <mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 10:51 AM To: <mailto:[email protected]> [email protected] Subject: Re: Witango-Talk: performance question I can tell you how I do it. Create a TCF that loads the domain vars in the oncreate event. I do this in a general widgets tcf. Then put this code at the top of any page that will access the domain vars. <!-- Check Peach Widgets Start Timer: <@timer> --> <@if "<@var domain$widgets type=text> contains 'Object'"> <!-- Just Checking the Peach Object Status Listener Address: <@var system$listenerAddress>:<@var system$listenerPort> Current Object: <@var domain$Widgets> --> <@else> <@assign domain$widgets <@CREATEOBJECT OBJECTID="widgets.tcf" TYPE="TCF">> <!-- Just Creating the Peach Object Status Listener Address: <@var system$listenerAddress> Created Object: <@var domain$widgets> --> </@if><!-- Check Peach Widgets End Timer: <@timer> --> You don't need all the timers and comments, but this is what I do, to see in source of page what is going on. so this code will make sure the object exists, if not create. To purge your domain vars, just create and don't check first. -- 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 <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] - <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] <http://bighead.net/> http://bighead.net/ - <http://eventpix.com/> http://eventpix.com/ On Feb 25, 2008, at 7:48 AM, Ted Wolfley wrote: Hi, All queries are indexed and I agree it would be a good idea to put the small data results into domain arrays. What is the best way to set the domain array, at witango server startup or schedule a taf to run? I forgot one important fact; the site has a page that is also being heavily hit by search bots, Last week, the site was hit by a google bot over 48,000 times in half a day. The Witango log is averaging 25 mg a day at logging level 1. We are also thinking of blocking the bots because the page they are hitting is only returning counts to a calling page. Ted _____ From: Robert Garcia [ <mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 10:17 AM To: <mailto:[email protected]> [email protected] Subject: Re: Witango-Talk: performance question I agree on indexing, but also, a good idea here, is to use the application scope, or the domain scope to cache this data. Unless this data is unique to each user. You just build controls to build your domain arrays, so that your apps have constant access to them, across users. -- 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 <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] - <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] <http://bighead.net/> http://bighead.net/ - <http://eventpix.com/> http://eventpix.com/ On Feb 25, 2008, at 7:07 AM, Stefan Gonick wrote: Hi Ted, >From your description it seems like you have an indexing issue. It shouldn't take so long to do those queries. You might want to look into coming up with good indexes to speed things up. Stefan At 10:05 AM 2/25/2008, you wrote: Hi, I have a website running on Windows 2003 using Witango server 5.5.003 pulling data from Sql Server 2000 on a Windows Storage Server 2003. In the taf, there is a group of about 8 database I/O that are used to fill small arrays (scope: request) for use in choice lists each time a page is called, The data will rarely change and never in the same session. The main function of the taf is to search the database and return the most recent 1000 results, if there are that many and putting the results into an user array, which works fine. The taf then display the array in results of 20 using the start and stop of the array loop. When going from one page to another, it takes about 6 seconds. Since the main data is already in an array, the only thing accessing the database is the 8 database I/Os. How much pagination speed would I pick up if I change the small database I/Os to run just once and use user arrays? Ted Wolfley Lead Internet and Database Programmer The Ogden Group of Rochester phone: 585.321.1060 x23 fax: 585.321.0043 <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] <http://www.ogdengroup.com /> http://www.ogdengroup.com <http://www.ogdengroup.com /> ________________________________________________________________________ TO UNSUBSCRIBE: Go to <http://www.witango.com/developer/maillist.taf> <http://www.witango.com/developer/maillist.taf> http://www.witango.com/developer/maillist.taf ===================================================== Database WebWorks: Dynamic web sites through database integration <http://www.databasewebworks.com/> http://www.DatabaseWebWorks.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to <http://www.witango.com/developer/maillist.taf> http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to <http://www.witango.com/developer/maillist.taf> http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to <http://www.witango.com/developer/maillist.taf> http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to <http://www.witango.com/developer/maillist.taf> http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to <http://www.witango.com/developer/maillist.taf> 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
