The best thing you can do is spend about an hour and test it out on your
site, on your code.
I have found that during my tests, there can actually be an increase in
execution time if you use lots of little cfoutputs rather than one big
cfoutput. I attribute this to CF having to fire up the cfoutput engine
(maybe?) then shut it down, then fire it up, and so on. Even for "normal"
amounts of cfoutputs on a page, I have found it is an almost unnoticeable
difference in speed to just wrap the entire page in cfoutput. THis of course
has the added benefit of being easier to code, thus faster, which means you
can ship earlier and take the money you would have spent on development and
but another processor for your CF box. :)
Do whatever you want with cfoutput - it basically hasn't mattered in tests
I've run.
Nat Papovich
ICQ 32676414
"If it was hard to write,"
says the Real Programmer,
"it should be hard to understand."
-----Original Message-----
From: Les Mizzell [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 6:23 AM
To: Fusebox
Subject: RE: cf_bodycontent
I'm interested in the performance aspects of <CFOUTPUT> as well....
What's better - a large block with 35 individual <CFOUTPUT> tags around 35
single elements, or the same block with just one <CFOUTPUT> at the head and
the close.....
For pages with a small number of <CFOUTPUT> tags, I've tended to use
individual tags around various elements. However, if there's a ton of tags
needed, I've tended to wrap the entire section in one <CFOUTPUT> tag
instead.
Thoughts?
Les Mizzell
***********
Some people say I'm too apathetic.
But why should I care?
> -----Original Message-----
> From: Erki Esken [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 10, 2000 9:23 AM
> To: Fusebox
> Subject: Re: cf_bodycontent
>
>
> I use the <cfsetting enableoutputonly="yes/no"> tag.
>
> BTW: In Ben Forta's Tips & Tricks of the ColdFusion Masters
> presentation theres:
>
> - <CFOUTPUT> is one of ColdFusion's most important tags
> - Any text within a <CFOUTPUT> block must be parsed and
> inspected - parsing takes time
> - Don't place text in between <CFOUTPUT> tags unnecessarily
>
> Sooo.. How do you do it? Do you use <cfoutput> around large blocks
> of code or more like this:
>
> <a
> href="index.cfm?fuseaction=<cfoutput>#attributs.fuseaction#</cfoutput>">
> </a>
>
> And has anyone measured how big is the performance hit when
> using a lot of text inside <cfoutput> tags versus <cfoutput>
> only around variables?
>
> Erki
>
> ----- Original Message -----
> From: "Lee Borkman" <[EMAIL PROTECTED]>
> To: "Fusebox" <[EMAIL PROTECTED]>
> Sent: Wednesday, October 11, 2000 5:08 AM
> Subject: Re: cf_bodycontent
>
>
> Hi Paul,
>
> If you strip the space using CF_BodyContent, you still get whitespace
> caused
> by the index.cfm, app_globals, etc. Best of all is to just enclose your
> entire index.cfm fusebox inside a CustomTag like CF_LessWhiteSpace (hey,
> that's one of mine!!) or Nate Weiss' CF_StripWhiteSpace (I think that's
> the
> name).
>
> Best of luck,
> Lee Borkman
> Bjork.Net - ColdFusion Tags by Bjork
>
> ----------------------
>
> "Paul Johnston" <[EMAIL PROTECTED]> wrote:
> Just a question. Using this tag could mean that we could strip
> whitespace
> from all pages. This could then cut down on download times without
> changing
> our coding structures methods etc.
>
> What do you think?
>
>
>
> ------------------------------------------------------------------
> ------------
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fu
sebox or send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body.
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
