- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Setting kernel params after Mem and CPU upgrad...
Operating System - HP-UX
1753599
Members
6228
Online
108796
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
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
Go to solution
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
04-23-2007 04:08 AM
04-23-2007 04:08 AM
Re: Setting kernel params after Mem and CPU upgrade?
wow, great. A bit too much hardware for me.
The output is in the attachment.
Thank you.
Regards,
Kalin
The output is in the attachment.
Thank you.
Regards,
Kalin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2007 05:16 AM
04-23-2007 05:16 AM
Re: Setting kernel params after Mem and CPU upgrade?
Looking at this output I can see that the LUN c4t0d0 is made up of 8 x 72GB disks in a RAID1+0 configuration to provide a 288GB LUN. I have to say that doesn't seem like much for a SAP BW environment to me, but I guess that depends on what you are doing with it... certainly I would expect the number of CPUs you have in the system now could more that max-out a single Smart Array card for IO.
Also as I pointed out earlier, all your reads and write are going to these 8 disks, which seems to me to probably be pretty inefficient.
Looking at the output there appears to be another drive configured (probably presented as c4t0d1) - what is that used for? I think you need to look at doing the SAP load so that it is reading from one set of disks and writing to another.
You could try upping the scsi queue depth, although I can't find a reccomended setting for the Smart Array card. It's probably safest to up it in small increments. If you see performance gains then keep going until you see no further perf gains, or start getting device queue full messages in the syslog.
I'd start with just 16 and see how that goes:
scsictl -m queue_depth=16 /dev/rdsk/c4t0d0
I'd be surprised if this makes much difference.
HTH
Duncan
I am an HPE Employee
Also as I pointed out earlier, all your reads and write are going to these 8 disks, which seems to me to probably be pretty inefficient.
Looking at the output there appears to be another drive configured (probably presented as c4t0d1) - what is that used for? I think you need to look at doing the SAP load so that it is reading from one set of disks and writing to another.
You could try upping the scsi queue depth, although I can't find a reccomended setting for the Smart Array card. It's probably safest to up it in small increments. If you see performance gains then keep going until you see no further perf gains, or start getting device queue full messages in the syslog.
I'd start with just 16 and see how that goes:
scsictl -m queue_depth=16 /dev/rdsk/c4t0d0
I'd be surprised if this makes much difference.
HTH
Duncan
I am an HPE Employee
- « Previous
- Next »
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP