GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Proliant BL465c-G6 and Processor Affinity
BladeSystem - General
1853501
Members
8802
Online
104088
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2010 06:36 AM
03-02-2010 06:36 AM
Proliant BL465c-G6 and Processor Affinity
We are running an ASP.NET application on a Proliant BL465c-G6 with 12 Cores (AMD Opteron 2435, 2.6 GHz).
On the previously used G1 Hardware with 4 Cores (AMD Opteron, 2.8 GHz) the execution time of the same request is 2 seconds, while on the newer G6 hardware it is 4 seconds.
If we configure processor affinity in .NET, so that the application is bound to a specific core, we get 2.3 seconds with the G6 hardware. But performance under stress (an external load balancer distributes the load to 12 identical applications and each application has its own dedicated CPU) is worse than in another configuration without affinity (all 12 applications can use any CPU).
Does anyone know, how to get the perfomance of the older G1 hardware, when the load is low, without having to use CPU affinity and thus loosing performance, when the load on the machine is high?
What is the difference between G1 and G6 hardware, which results in almost half the performance of the newer hardware?
Might there be any BIOS setting, that could influence performance so much?
The OS is Windows Server 2003 Enterprise SP2 in both cases. The application uses .NET Framework 3.5, but most of the execution time is consumed in a 3d-party COM component (.NET COM Interop).
Best regards,
Gerhard
On the previously used G1 Hardware with 4 Cores (AMD Opteron, 2.8 GHz) the execution time of the same request is 2 seconds, while on the newer G6 hardware it is 4 seconds.
If we configure processor affinity in .NET, so that the application is bound to a specific core, we get 2.3 seconds with the G6 hardware. But performance under stress (an external load balancer distributes the load to 12 identical applications and each application has its own dedicated CPU) is worse than in another configuration without affinity (all 12 applications can use any CPU).
Does anyone know, how to get the perfomance of the older G1 hardware, when the load is low, without having to use CPU affinity and thus loosing performance, when the load on the machine is high?
What is the difference between G1 and G6 hardware, which results in almost half the performance of the newer hardware?
Might there be any BIOS setting, that could influence performance so much?
The OS is Windows Server 2003 Enterprise SP2 in both cases. The application uses .NET Framework 3.5, but most of the execution time is consumed in a 3d-party COM component (.NET COM Interop).
Best regards,
Gerhard
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP