Sponsored Content
Full Discussion: optimizing disk performance
Special Forums Hardware Filesystems, Disks and Memory optimizing disk performance Post 22959 by Perderabo on Thursday 13th of June 2002 12:15:43 PM
Old 06-13-2002
Quote:
Originally posted by J.P

And yet another hard disk tip i got from another book. It claims I'll get slightly better performance if I split my linux installation on several disks since more disk heads are working on the operating system. True, or just another worthless statement?

Thanks again
/J.P
That is absolutely true. At some point you have so many drives on an i/o path that they must wait for each other. Until you reach that point, the more drives the better.

I'm not a linux expert. But on HP-UX, there are several ways to exploit more drives. One way is to just use raids. They are a collection of drives that look like one drive to the os. But also with individual drives, HP (under LVM) supports striping. This lets you distribute a logical disk over several physical disks. HP also supports disk mirroring. With mirrors, a write must go to 2 or more drives, so writes take longer. But a read can come from any drive so reads are quicker. Since you usually read much more often than you write, this is a performance win.

If you don't have stuff like this on linux, then you can still work at the application level. It's not enough to just have the drives, they must be involved with your i/o intensive work. You may be able to one file on one drive, another file on the next drive and so on.
 

7 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

Optimizing Apache Server Performance

I found this link useful in a discussion about Apache performance tuning: http://www.serverwatch.com/tutorials/article.php/3436911 (0 Replies)
Discussion started by: Neo
0 Replies

2. AIX

disk performance

Hello, I have a aix 570 system with san disk. I do write test of performance in a lv with four disk. While the test I run filemon tools for trace the disk activity. The outputs of filemon are at the en of this message. I see my lV(logical volume) throughput at 100 meg by second. 2 of 4 disk... (0 Replies)
Discussion started by: Hugues
0 Replies

3. Red Hat

Linux disk performance

I am getting absolutely dreadful iowait stats on my disks when I am trying to install some applications. I have 2 physical disks on which I have created 2 separate logical volume groups and a logical volume in each. I have dumped some stats as below My dual core CPU is not being over utilised... (3 Replies)
Discussion started by: jimthompson
3 Replies

4. Red Hat

Disk performance problem on login

Running CentOS 5.5: I've come across a relatively recent problem, where in the last 2 months or so, the root disk goes to 99% utilization for about 20 seconds when a user logs in. This occurs whether a user logs in locally or via ssh. I have tried using lsof to track down the process that is... (5 Replies)
Discussion started by: dangral
5 Replies

5. Solaris

disk performance

What tools/utilities do you use to generate metrics on disk i/o throughput on Solaris. For example, if I want to see the i/o rate of random or sequential r/w. (2 Replies)
Discussion started by: dangral
2 Replies

6. Linux

Disk Performance

I have a freshly installed Oracle Linux 7.1 ( akin to RHEL ) server. However after installing some Oracle software, I have noticed that my hard disk light is continually on and the system performance is slow. So I check out SAR and IOSTAT lab3:/root>iostat Linux... (2 Replies)
Discussion started by: jimthompson
2 Replies

7. Debian

Optimizing exim performance

Hi, Recently, I experienced that exim was slow in sending outgoing mail, it was spending a lot of time in the queue, resulting in customer complains. I came across an article in the internet to optimize the performance of exim in the server. However, the location of the exim.conf is not in... (0 Replies)
Discussion started by: anaigini45
0 Replies
SD(4)							     Linux Programmer's Manual							     SD(4)

NAME
sd - driver for SCSI disk drives SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */ #include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */ CONFIGURATION
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti- tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive. SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num- ber is the number of the physical drive in order of detection, and partition_number is as follows: +3 partition 0 is the whole drive partitions 1-4 are the DOS "primary" partitions partitions 5-8 are the DOS "extended" (or "logical") partitions For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system. At this time, only block devices are provided. Raw devices have not yet been implemented. DESCRIPTION
The following ioctls are provided: HDIO_GETGEO Returns the BIOS disk parameters in the following structure: struct hd_geometry { unsigned char heads; unsigned char sectors; unsigned short cylinders; unsigned long start; }; A pointer to this structure is passed as the ioctl(2) parameter. The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters. BLKGETSIZE Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long. BLKRRPART Forces a reread of the SCSI disk partition tables. No parameter is needed. The SCSI ioctl(2) operations are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl(2) fails with the error EINVAL. FILES
/dev/sd[a-h] the whole device /dev/sd[a-h][0-8] individual block partitions COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 SD(4)
All times are GMT -4. The time now is 10:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy