On 2007.04.26, Jade Rubick <[EMAIL PROTECTED]> wrote: > I was wondering if there was any obvious problems with redefining > procs repeatedly. > > For example, if a page contained a proc definition which was sourced > on each page. > > I wasn't sure of the underlying scalability issues that could arise > from this. Any insights?
If you've profiled the page performance and it's acceptable, then you're okay. The consequence of repeatedly redefining a proc is that time is spent byte-compiling the script only to be thrown away when the proc gets redefined. If that overhead cost isn't materially impacting your page execution performance, then I guess you don't need to worry about it. Later, if you're trying to micro-optimize because you need to serve more requests per second, refactoring such that your procs only get defined once per Tcl interp startup would be obvious low hanging fruit. -- Dossy -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
