I can't really think of any way to do it without processing overhead,
cfthread would be the obvious choice, and an event gateway will use up a
request in just the same way as cfthread.
Upgrading to cfenterprise would be the obvious choice so you can have more
threads and additional instances, but if this is not an option for you,
then how about installing a copy of railo and give that a try, even if you
only use it for processing logging and stuff like that it at least gives
you some extra threads outside of CF.

Another little trick is that you switch CF back to developer mode which
gives you all the enterprise features, and create a new instance, then put
your std license back in. You lose all the enterprise options again, but
the instance you create is still running, and you can start/stop it, use
its cfadmin etc.


On Mon, Apr 16, 2012 at 3:21 AM, Dave Watts <dwa...@figleaf.com> wrote:

>
> > We're trying to determine what would be the most effective way to do
> "fire
> > and forget" logging in our CMS / CRM system.  The goal is to improve
> > performance by not having the page loads have to wait for the logging
> > portion of the code.  We would like it to be a usable solution on CF
> > Standard 9 (and possibly earlier versions).  We've used cfthread a bit
> for
> > this and it works pretty well.  But, the concern is that CF Standard
> limits
> > the number of threads you can use (to 10, I think).
> >
> > We've looked at using an event gateway too, which seems like it would be
> a
> > great solution but my understanding is that this is also throttled to
> some
> > extent on CF 9 to some extent.  So, I'm not sure if we would face a
> > bottleneck problem that way.
> >
> > Are there other alternatives that we're not thinking about?
>
> Perhaps you could do the logging in onRequestEnd, after returning the
> page to the browser using CFFLUSH? The user wouldn't have to wait, in
> that case, although other users' requests may end up in the queue a
> bit longer.
>
> You might also spend some time minimizing the work that logging does.
> Are you logging to a database? Maybe you could defer that, and write
> to a file (should generally be faster), then later on use a scheduled
> task (or some other alternative outside of CF) to read the file into
> the database.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
> http://training.figleaf.com/
>
> Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on
> GSA Schedule, and provides the highest caliber vendor-authorized
> instruction at our training centers, online, or on
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:350707
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to