- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: HD Partitioning
Operating System - Linux
1753424
Members
4681
Online
108793
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
10-06-2009 09:25 AM
10-06-2009 09:25 AM
Re: HD Partitioning
I've run the same test with only one disk and I think there is a significant difference when it comes to sequential read write. But look for yourselves the bonnie++ output data is attached to the topic.
Some info about the test:
It was done on a DL380G5 with only one 146GB 10K SAS drive.
The server has a BBWC module and the cache setting was set to default.
(75% write adn 25% read if Iâ m not mistaken)
P01.html is the first 10% of the disk
P02.html the last 10.%
file system was ext3.
I used the following command:
Bonnie++ -u root â p /mnt/p01 â q >> p01.csv
Some info about the test:
It was done on a DL380G5 with only one 146GB 10K SAS drive.
The server has a BBWC module and the cache setting was set to default.
(75% write adn 25% read if Iâ m not mistaken)
P01.html is the first 10% of the disk
P02.html the last 10.%
file system was ext3.
I used the following command:
Bonnie++ -u root â p /mnt/p01 â q >> p01.csv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2009 09:50 AM
10-06-2009 09:50 AM
Re: HD Partitioning
In the old days there were X sectors per track regardless of whether it was on the outer or inner rings of the disk. Today, drive manufacturers optimize around the areal density of the media and cram as many sectors as the media allows into each and every track, basically giving the effect of a constant linear velocity data stream to the head.
The operating system's idea of the geometry of a drive is radically different than its physical layout (query the drive and then compare it to the drive's data sheet). You could think you're writing to a track that's in the inner diameter, and in reality you're writing partial tracks somewhere in the middle, and you actually suffer a performance loss because there's a head position move in there in the middle.
Nothing you can do about it, though--the drive's firmware is in control.
The operating system's idea of the geometry of a drive is radically different than its physical layout (query the drive and then compare it to the drive's data sheet). You could think you're writing to a track that's in the inner diameter, and in reality you're writing partial tracks somewhere in the middle, and you actually suffer a performance loss because there's a head position move in there in the middle.
Nothing you can do about it, though--the drive's firmware is in control.
- « Previous
-
- 1
- 2
- 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