On Mon, May 7, 2012 at 4:28 PM, .jonah <[email protected]> wrote:
> Even some judicious just of <cfcache> will get you a long way. Yup. For us, the expensive stuff was unique per page, but also part of the problem that we never seemed to be able to get a handle on was the concurrency demands associated with having bots hit as many pages as they could with as many threads as you set the CF server to allow. For that matter, if there are common queries you can get an enormous amount of mileage out of short query caches of two or three seconds in duration. For example, on one of those listings, say the dealer info is a query. The bot could hit the dealer's listings as a block, so if you cache the dealer's data for lets say ten seconds, you can eliminate a ton of hits to the db... and since the cache is short lived, there's room for all of the other hundreds of dealers whose material is being accessed - and hopefully cached to good effect - at the same time. Turning CF into a backend processor-only is no small task. Its not something you can do without a whole lot of planning and effort, which is a good thing because unless you really need to, you shouldn't. Something else to consider is rel=nofollow and hope you can exert some control over redundant traffic flow. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:351034 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
