Locking has almost no performance penalty in and of itself, so there is nothing to add to the amount of time the code being locked take to process. 1 cfset is going to take almost no time at all, so you could safely put the timeout at 1 second, because even if CF was totally maxed on threads with 5, 10, or 20, etc pages executing at once, and they all hit that one cfset at the same time, that cfset is still probably going to execute faster than threads * processing time.
So as Dave said, it really depends on what is being done in the lock. Personally I usually default to 5 seconds, even for 1 cfset. If a 5 second lock it timing out, then I'm probably doing something wrong in the first place. -- jon mailto:[EMAIL PROTECTED] Monday, September 23, 2002, 10:32:35 AM, you wrote: TW> yeah, I get that, but I guess what im looking for is something like... TW> 1 cfset = wait for processing 1 sec. TW> 1 cfset + 1 whatever = wait for proc. 2.5 secs. TW> are there any metrics or best practices for this? TW> ..tony TW> Tony Weeg TW> Senior Web Developer TW> Information System Design TW> Navtrak, Inc. TW> Fleet Management Solutions TW> www.navtrak.net TW> 410.548.2337 TW> -----Original Message----- TW> From: Dave Watts [mailto:[EMAIL PROTECTED]] TW> Sent: Monday, September 23, 2002 10:35 AM TW> To: CF-Talk TW> Subject: RE: cflocking de-mystified (was RE: WHYYYYY!!!!!!) >> now, I guess my next question would be, is the cflock >> timeout sort of an arbitrary guess as to what would be >> a good amount of time? I mean, how long are the lock >> timeouts on the heaviest hit cf pages set for? whats >> a good number? TW> 42. TW> Seriously, the number will depend on what you're doing inside the lock, TW> and TW> how critical it is to wait for that lock as opposed to cancelling the TW> request. Just remember that the timeout specifies how long CF will wait TW> to TW> execute that lock, not how long it'll hold the lock. That is, if CF has TW> to TW> wait because another request is using the lock, the timeout is how long TW> CF TW> will wait. ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
