From: Richard Nutman <Richard.Nutman@s-a-m.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Temperature of CPU when running DPDK App
Date: Thu, 29 Mar 2018 10:05:52 +0000 [thread overview]
Message-ID: <733AB18813E3864094592CC5191B172A235BC96B@EX-UKHA-01.ad.s-a-m.com> (raw)
In-Reply-To: <287310953.2822437.1522234072488.JavaMail.zimbra@viettel.com.vn>
Hi,
72c looks to be well within range from the sensor specs you posted below.
You say you have a problem with it, what exactly is the problem ?
Thermal throttling will kick in before the cpu damages itself.
As others have stated you may want to look at inserting some _mm_pause instructions which halt the cpu for around 20-40 cycles and help to reduce heat.
Other than that perhaps look to see if the server is getting adequate cooling. There is no recommended temperature for DPDK, if the cpu is well within limits then there are no problems.
-Richard.
> -----Original Message-----
> From: vuonglv@viettel.com.vn [mailto:vuonglv@viettel.com.vn]
> Sent: 28 March 2018 11:48
> To: users@dpdk.org
> Cc: toanln1
> Subject: [dpdk-users] Temperature of CPU when running DPDK App
>
>
>
> Hi DPDK team,
> I have big problem with temperature of CPU when running DPDK App (My
> app use all of 16 CPU on socket 1, and all CPU always run with 100%
> work load). As you see in below statistics, temperature of CPU is up to
> 72°C.
> My question: 72°C is too hot, right?. What is the recommend for
> temperature of CPU when running DPDK App?
>
>
>
>
> Server: HP-BL460C Gen9
> OS: Redhat 7.3
>
> [root@localhost dataplane]# lscpu
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 64
> On-line CPU(s) list: 0-63
> Thread(s) per core: 2
> Core(s) per socket: 16
> Socket(s): 2
> NUMA node(s): 2
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 79
> Model name: Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz
> Stepping: 1
> CPU MHz: 2600.000
> BogoMIPS: 5200.76
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 40960K
> NUMA node0 CPU(s): 0-15,32-47
> NUMA node1 CPU(s): 16-31,48-63
>
> [root@localhost ~]# sensors
> ixgbe-pci-0600
> Adapter: PCI adapter
> loc7: +33.0°C (high = +95.0°C, crit = +75.0°C)
>
> power_meter-acpi-0
> Adapter: ACPI interface
> power1: 0.00 W (interval = 300.00 s)
>
> coretemp-isa-0000
> Adapter: ISA adapter
>
> Physical id 0: +61.0°C (high = +83.0°C, crit = +93.0°C)
> Core 0: +55.0°C (high = +83.0°C, crit = +93.0°C)
> Core 1: +54.0°C (high = +83.0°C, crit = +93.0°C)
> Core 2: +54.0°C (high = +83.0°C, crit = +93.0°C)
> Core 3: +54.0°C (high = +83.0°C, crit = +93.0°C)
> Core 4: +56.0°C (high = +83.0°C, crit = +93.0°C)
> Core 5: +53.0°C (high = +83.0°C, crit = +93.0°C)
> Core 6: +53.0°C (high = +83.0°C, crit = +93.0°C)
> Core 7: +53.0°C (high = +83.0°C, crit = +93.0°C)
> Core 8: +52.0°C (high = +83.0°C, crit = +93.0°C)
> Core 9: +52.0°C (high = +83.0°C, crit = +93.0°C)
> Core 10: +52.0°C (high = +83.0°C, crit = +93.0°C)
> Core 11: +52.0°C (high = +83.0°C, crit = +93.0°C)
> Core 12: +52.0°C (high = +83.0°C, crit = +93.0°C)
> Core 13: +53.0°C (high = +83.0°C, crit = +93.0°C)
> Core 14: +53.0°C (high = +83.0°C, crit = +93.0°C)
> Core 15: +54.0°C (high = +83.0°C, crit = +93.0°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
>
> Physical id 1: +72.0°C (high = +83.0°C, crit = +93.0°C)
> Core 0: +72.0°C (high = +83.0°C, crit = +93.0°C)
> Core 1: +71.0°C (high = +83.0°C, crit = +93.0°C)
> Core 2: +69.0°C (high = +83.0°C, crit = +93.0°C)
> Core 3: +67.0°C (high = +83.0°C, crit = +93.0°C)
> Core 4: +70.0°C (high = +83.0°C, crit = +93.0°C)
> Core 5: +71.0°C (high = +83.0°C, crit = +93.0°C)
> Core 6: +70.0°C (high = +83.0°C, crit = +93.0°C)
> Core 7: +70.0°C (high = +83.0°C, crit = +93.0°C)
> Core 8: +70.0°C (high = +83.0°C, crit = +93.0°C)
> Core 9: +69.0°C (high = +83.0°C, crit = +93.0°C)
> Core 10: +71.0°C (high = +83.0°C, crit = +93.0°C)
> Core 11: +71.0°C (high = +83.0°C, crit = +93.0°C)
> Core 12: +70.0°C (high = +83.0°C, crit = +93.0°C)
> Core 13: +68.0°C (high = +83.0°C, crit = +93.0°C)
> Core 14: +70.0°C (high = +83.0°C, crit = +93.0°C)
> Core 15: +69.0°C (high = +83.0°C, crit = +93.0°C)
>
>
>
>
> Many thanks,
>
> Vuong Le
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
prev parent reply other threads:[~2018-03-29 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <126402432.2812576.1522233938671.JavaMail.zimbra@viettel.com.vn>
2018-03-28 10:47 ` vuonglv
2018-03-28 11:08 ` Vincent Jardin
2018-03-28 12:24 ` Wiles, Keith
2018-03-28 13:19 ` Dai, Wei
2018-03-29 14:34 ` vuonglv
2018-03-29 10:05 ` Richard Nutman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=733AB18813E3864094592CC5191B172A235BC96B@EX-UKHA-01.ad.s-a-m.com \
--to=richard.nutman@s-a-m.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).