CFUnited 2008:
Calendar
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
Recent Entries
Come On In, Rails-The Water's Warm
Shan's Simple Examples: File uploads with Flex and ColdFusion
Recent Comments
Google Calendar API - Creating a new Calendar with ColdFusion
Steve Julian said: When and where are you going to post the finished CFC's ? Thanks
[more]
Three Phases of Programmer Development
Pat Branley said: I normally think of those phase 2 people as 'programmers' and the phase 3 people as 'developers'.
I...
[more]
New Job Title: Front End Engineer
Sean Corfield said: Well, there's always the excellent Fusion Authority Quarterly Journal...
[more]
Down To The Wire: HTTP Sniffers
Brian M said: I second the mention of the Charles Web Debugging Proxy that Tariq mentioned. It is fantastic. It s...
[more]
New Job Title: Front End Engineer
Patrick said: Heya Sean. Good point. I never understood how they did things over there at SysCon, and I understand...
[more]
Archives By Subject
Business of Software (4) [RSS]
ColdFusion (318) [RSS]
Conferences (6) [RSS]
Databases (87) [RSS]
Flex & Flash (109) [RSS]
Fusebox (87) [RSS]
General Development (29) [RSS]
Google (9) [RSS]
Hardware (5) [RSS]
JVM & Java (132) [RSS]
Linux (20) [RSS]
Miscellaneous (254) [RSS]
Performance (8) [RSS]
SeeFusion (36) [RSS]
Shan's Simple Examples (6) [RSS]
User Interface (3) [RSS]
Windows (5) [RSS]
Archives By Poster
Daryl Banttari (10)
Nat Papovich (29)
Patrick Quinn (36)
Shannon Hicks (22)
Steve Nelson (21)
Tyson Vanek (3)
CFDocument performance
I've been building an app that uses CFDocument to build out some FlashPaper and PDF's. Everything was working great on my local development box, but when I pushed it to my production box, generation of both the FlashPaper and PDF files was taking forever. Processing time went from 4-5 seconds to 3-6 minutes.
Eventually, I tracked down this newsgroup post, which suggested moving all the CF processing out from between the CFDocument tags. I used CFSaveContent to save my output to a variable, and put just that variable between the CFDocument tags, and my performance problems went away.
The funny thing is, my server wasn't CPU, Memory or Disk bound. In fact, the stack trace in SeeFusion said that the thread generating the CFDocument was actually waiting. So, that thread was basically sitting there doing nothing for minuets at a time. Hopefully this saves someone else an hour or so looking for the problem and solution.
If you have images in the CFDocument that are being accessed on the same server...make sure to use a "file:/" url to access them instead of a regular HTTP url because it will force a web request to the server for each one instead of just quickly loading the file from disk.
This helped me a lot on a few reports.
Mike.
When styling a documents with CFDOCUMENT always use the @import to include the css. For some odd reason not only does this give better performance, it will take care of the problems most people have with CFDOCUMENT not rendering the style correctly.
The short story is we converted any images to png's (using CFX_ImageCR3) and our performance problems disappeared. In fact, generating a PDF is now 8 or 9 times faster.
Macromedia/Adobe must mangle the jpeg conversion/resample/resize when they add them to the PDF.
file:///misc2/images/ does not work. Surely, this is possible without having to map the drive