[Spread-users] main concern on High CPU utilization

Sandeep Jeevan sandeep.jeevan at vnl.in
Tue Mar 10 05:28:34 EDT 2009


Hi John

Yes I had tried both the configuration but both of them shows same CPU utilization .

I am unable to take the snapshot of that but I had upgraded to 4.0.0 its is now taking around 16% to 17% CPU for same number of messages .In v 3.17.4 I had not made the changes to To_hold_token()

Currently I am trying to go through the changes made in the version 4.x.x



Sandeep jeevan

VNL  | 246, Phase IV, Udyog Vihar, Gurgaon, Haryana 122 015, INDIA | +91-124-4311600-609 | F +91-124-4104766 | www.vnl.in

-----Original Message-----
From: John Lane Schultz [mailto:jschultz at spreadconcepts.com]
Sent: Monday, March 09, 2009 7:13 PM
To: Sandeep Jeevan
Cc: spread-users at lists.spread.org
Subject: Re[2]: [Spread-users] main concern on High CPU utilization



Hi Sandeep,



Did you try the unicast configuration I recommended to you?  Did it make any difference?  Do you have the output from sp_monitor, both for the multicast and unicast configurations I recommended to you?  Can you post them in an email?  Did you upgrade to v3.17.4? And/or did you make the change to To_hold_token() as we discussed?



It very well could be that the load you are seeing is how Spread runs on your particular CPU with that level of traffic going through it;  as I said, it is a bit of a CPU hog.  On top of the line Intel processors running linux (fedora), Spread can push a couple hundred Mega BITS per second before it becomes CPU or scheduling limited.



Cheers!

John



---

John Lane Schultz

Spread Concepts LLC

Phn: 443 838 2200

Fax: 301 560 8875



Monday, March 9, 2009, 4:44:25 AM, you wrote:





Yes that's right it's a flavor of Linux (it is a real time operating system )

Its shows 30 % under load I am sending 1352 messages per second from the client to daemon.

Vendor      freescale

Processor   MPC8560

busFreq     833.333325Mhz

memory      1024 MB

I had upgraded to 4.x.x it had reduced the CPU to 17% can it be further decreased to under 10%.

I am sending 1352 packets ranging from(800 bytes to 1500 bytes) in a sec.

And no it is not a "G4" and "G3"





Sandeep jeevan

Member Technical(Stack)

Mob:9717892153

VNL  | 246, Phase IV, Udyog Vihar, Gurgaon, Haryana 122 015, INDIA | +91-124-4311600-609 | F +91-124-4104766 | www.vnl.in









-----Original Message-----

From: Alexey Zakhlestin [mailto:indeyets at gmail.com]

Sent: Monday, March 09, 2009 12:46 PM

To: Sandeep Jeevan

Cc: Christopher Browne; spread-users at lists.spread.org; John Lane Schultz

Subject: Re: [Spread-users] main concern on High CPU utilization



On Mon, Mar 9, 2009 at 7:16 AM, Sandeep Jeevan <sandeep.jeevan at vnl.in> wrote:

> Hi

> Sorry for not correctly identifying the things said to me .

> I am using monta vista (operating system ) running on power P.C architecture



which is... kind of linux. right?



> But is it going to have any concern regarding the CPU utilization on that particular architecture.



Does it show 30% of utilization in the calm state or under load?

What kind of load do you have? (number of messages per second)

What is the speed of CPU? Is it so called "G4" or "G3" CPU?



John asked you to upgrade to 3.17.4. Сan you do that? Does it help?



--

Alexey Zakhlestin

http://www.milkfarmsoft.com/

The information contained in this e-mail is private & confidential and may also be legally privileged. If you are not the intended recipient, please notify us, preferably by e-mail, and do not read, copy or disclose the contents of this message to anyone.
The information contained in this e-mail is private & confidential and may also be legally privileged. If you are not the intended recipient, please notify us, preferably by e-mail, and do not read, copy or disclose the contents of this message to anyone.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.spread.org/pipermail/spread-users/attachments/20090310/bece7491/attachment.html 


More information about the Spread-users mailing list