ColdFusion Muse

Sick Server Troubleshooting Part 3 - In the Soup

Mark Kruger August 12, 2008 9:27 PM Coldfusion Troubleshooting Comments (2)

Ok... you've made config changes and tested your connections and performance and you know with the certainty of Rush Limbaugh making a right turn that the server is fully tuned and as lean and mean as possible, but you still have a problem. Now what? Well, it's time to look at the code. Start by enabling slow page logging in the CF admin during a high traffic low performance period. Take the list of templates that are running slow and start digging into them to determine why they are dragging their little cyber feet.

Here are a couple of code related items that you might be looking for.

Read More
  • Share:

2 Comments

  • ike's Gravatar
    Posted By
    ike | 8/13/08 9:02 AM
    Something CF8 specific... The new CFThread tag opens up some interesting new opportunities for unexpected server sickness... Two things in particular to remember

    1) there's a limit (defualt is 8) to the number of simultaneous running threads, and you'll get errors if a request can't get access to an available thread from that pool in a short period of time. So while it may seem like a logical thing to use cfthread to resize images, I know from personal experience that you have to be really careful about how you implement that (because I fouled up a server that way).

    2) read the docs real carefully for the section about how it duplicates any values that are passed into the thread arguments - all it takes is stuffing a CFC into a cfthread attribute and viola, memory leak ... it could be nothing, it could just be duplicating that 1 CFC -- or it could be that you duplicate a ton of CFC's that you didn't mean to because it contains a pointer to a factory full of CFCs in your application scope.

    Not really part of the tip, but this is something I don't like about the ColdBox object caching utility. It reaps its cache at the beginning of the request, which means the user has to wait for the cache utility to reap and to get around having the user wait, it uses cfthread if it's available (which takes up one of your available threads). A much better solution would have been to use cfflush at the end of the request and then reap after the content had been delivered to the browser, which would work on CF7, deliver content quickly and not use up an extra thread. Unfortunately the ColdBox caching utility isn't written that smartly.
  • Handbag's Gravatar
    Posted By
    Handbag | 1/23/09 8:00 PM
    Replica Handbags
    Our site offers fashion replica Louis Vuitton handbags, Fashion replica Bally hanbags, Fashion Balenciaga handbags, Fashion Chanel handbags, Fashion Chloe handbags, Fashion Christian Dior handbags, Fashion Dolce & Gabbana handbags, Fashion Fendi handbags, Fashion Gucci handbags, Fashion Hermes handbags, Fashion Coach handbags ,Fashion Versace handbags, Fashion Prada handbags, Fashion Yves Saint Laurent handbags, Fashion Marc Jacobs handbags, Fashion Jimmy Choo handbags, Fashion Loewe handbags, Fashion Miu Miu handbags, Fashion Mulberry handbags, Fashion Thomas Wylde handbags.www.good-handbag.com