GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- Superdome2 and hyperthreading enabled at the hardw...
Integrity Servers
1849171
Members
7613
Online
104041
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
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
11-15-2010 07:41 AM
11-15-2010 07:41 AM
Superdome2 and hyperthreading enabled at the hardware level.
So, I've got a question re: Superdome2 running HPUX 11.3 (Tukwilla).
I've been told that having hyperthreading turned on at the hardware level, but not at the OS level will affect performance, in that the even though the OS doesn't recognize it, the hardware layer underneath is still trying to implement and use the extra "chips" if you will. I've been told this does adversely affect performance.
Does anyone have documents or a reference to this as being a fact, or not a fact?
And, in case you're wondering why I'd have it turned on at the hardware layer and not at the OS: When it's running as an OLTP system during the day, it runs much better with hyperthreading turned off at the OS layer (and this is common), but at night, when almost no users are on the system, batch processing of all kinds of things run better with hyperthreading turned on. Well, since it's a dynamic setting, we plan to use it that way.
So, if anyone has seen something showing that I'm hurting day time OLTP performance by having it turned off at the OS level, but still on at the hardware level, or documents that state the opposite, please let me know.
Much appreciated!
I've been told that having hyperthreading turned on at the hardware level, but not at the OS level will affect performance, in that the even though the OS doesn't recognize it, the hardware layer underneath is still trying to implement and use the extra "chips" if you will. I've been told this does adversely affect performance.
Does anyone have documents or a reference to this as being a fact, or not a fact?
And, in case you're wondering why I'd have it turned on at the hardware layer and not at the OS: When it's running as an OLTP system during the day, it runs much better with hyperthreading turned off at the OS layer (and this is common), but at night, when almost no users are on the system, batch processing of all kinds of things run better with hyperthreading turned on. Well, since it's a dynamic setting, we plan to use it that way.
So, if anyone has seen something showing that I'm hurting day time OLTP performance by having it turned off at the OS level, but still on at the hardware level, or documents that state the opposite, please let me know.
Much appreciated!
We are the people our parents warned us about --Jimmy Buffett
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2010 09:37 AM
11-15-2010 09:37 AM
Re: Superdome2 and hyperthreading enabled at the hardware level.
The only information I found regarding this is
"NOTE: Once hyperthreading is enabled for an nPartition, it is still necessary to configure that partition's operating system to use it. For HP-UX, this means changing the value of the kernel parameter lcpu_attr to 1."
So I think the main difference between SD2 and older systems is, it is now enabled by default, for previous systems it was disabled by default.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
"NOTE: Once hyperthreading is enabled for an nPartition, it is still necessary to configure that partition's operating system to use it. For HP-UX, this means changing the value of the kernel parameter lcpu_attr to 1."
So I think the main difference between SD2 and older systems is, it is now enabled by default, for previous systems it was disabled by default.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
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