Sorry I meant to say it DOES seem like one core is commonly over utilized.

On Mon, Aug 15, 2011 at 1:12 PM, Dan Baughman <[email protected]>wrote:

> So what you are saying is that threads will use different cpu's
> automatically?
>
> Well in my case, I have quad quad cores, so its 16 cores. I do this on a
> bunch of servers and it just doesn't seem like one core is utilized a lot
> more than others by the jrun.exe.
>
> While each request should use or re-use a separate available worker thread
> it is my concern that this threads execute predominantly (or entirely) on
> one CPU.
>
>
>
> On Mon, Aug 15, 2011 at 12:58 PM, David McGuigan 
> <[email protected]>wrote:
>
>>
>> Are you saying that one of your cores has high utilization and the others
>> none? Your server should use all cores *as necessary* *if ever necessary*
>> *automatically* *without the intervention or management of your
>> application*.
>>
>> That said you can break certain parts of code off into separate threads
>> using the cfthread tag, but that's to make a specific URL or process more
>> performant by prioritizing or simulprocessing code chunks, not to try to
>> balance workload across multiple cores or processors.
>>
>>
>>
>>
>> On Mon, Aug 15, 2011 at 12:53 PM, Dan Baughman <[email protected]
>> >wrote:
>>
>> >
>> > With the one jrun.exe process running, I can never get coldfusion to
>> really
>> > utilize multiple processors.
>> >
>> > Is there a way in enterprise mode that you can set it to spawn multiple
>> > jrun.exe processes, one per processor to work collaboratively serving
>> one
>> > web site?
>> >
>> >
>> >
>>
>> 

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

Reply via email to