Alan be reasonable, lower your thread count man!!  

Hee hee, just kidding.  I've had the same issue as you.  You can have lots
of threads waiting for something to happen.  In my case, a slow expensive
database. In your case, cflocks or whatever.  We had to raise our threads a
fair bit higher than what is typically recomended to keep people from
getting qued.  Qued people are annoyed people.  I ve surmised that a waiting
thread doesnt take up much cpu time.

Basically, you have to lower you milliseconds per page.  I'm usually annoyed
if a page takes over 80 miliseconds to execute.  But youre stuck with your
file writing scheme.  Hmm, just a thought, if you do cffile and write the
var to your user, you can probably speed that by just cfincluding the file
to the page.  I think its easier on the system than cffile.  Java io but I'm
repeating that.

Good luck.

DRE
-----Original Message-----
From: Alan Ford [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 1:19 PM
To: CF-Talk
Subject: CFMX performance issue


>but I think at
>the very least it shows that 200 simultaneous threads is massive overkill.

Ok, already :-)

Forget 200 - I've reset it to 96.

Now, to everyone who is saying that 96 is too high my own experience of
trying to keep the site running smoothly at all costs is that an SRR of 96
is *way* better than 20. This is experience of coping with overloads on a
daily basis for 3 weeks or so.

It does not reduce the number of times the number of running threads grows
(nor does it increase it), but it does reduce dramatically the number of
times that cfmx has to queue threads and the recovery when it is not queuing
is much faster than when it is. With SRR set to 20 it was not unusual to
have cfmx queuing 20 times a day or more. Almost every timed it queued I had
to intervene. Now 2 or 3 is the norm, and the 17 other times when the thread
count grows it recovers quickly without queuing. I now have to intervene
once or twice a day (though unfortunately I still have to watch it like a
hawk!). (By intervene I mean restrict the max number of connections in IIS
down to about 300. cfmx recovers, I reset the connections to unlimited).

This business about 4 threads per processor is from CF 4 days. Surely the
calculation is different with cfmx, simply because it's a completely
different engine?

Alan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq

Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. 
http://www.fusionauthority.com/ads.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to