Sponsored Content
Full Discussion: optimizing disk performance
Special Forums Hardware Filesystems, Disks and Memory optimizing disk performance Post 22895 by J.P on Wednesday 12th of June 2002 07:15:23 PM
Old 06-12-2002
Question optimizing disk performance

I have some questions regarding disk perfomance, and what I can do to make it just a little (or much Smilie) more faster.

From what I've heard the first partitions will be faster than the later ones because tracks at the outer edges of a hard drive platter simply moves faster. But I've also read in a book that most-used partitions should be placed in the middle of a range of partitions. This doesn't make much sense to me.
Does this "put-heavily-accessed-in-the-middle" thing apply to logical partitions?

Should the heavily accessed partition really go in the middle? Even if the first partitions are large in size and later are small, thus leaving the heavily accessed partition "nearer" the center (where the platter moves slower)... ?

Any other suggestions like partition layout, filesystem recommendation etc are highly appreciated Smilie

I'm working with a linux system using a server software that does a lot of reading and writing so every bit of speed I can gain is valueable.

Thanks in advance

Last edited by J.P; 06-12-2002 at 08:21 PM..
 

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
PARTITION(8)						      System Manager's Manual						      PARTITION(8)

NAME
partition - make a partition table SYNOPSIS
partition [-mf] device [type:]size[+*] ... DESCRIPTION
Partition makes a partition table on device using the types and sizes given. It may be used in combination with repartition(8) for auto- matic installation of Minix. You may give up to four type:size[+*] specifications for the partitions. You may also specify holes before, between, and after the parti- tions. A hole differs from a partition specification by not having a type. The first hole is by default 1 sector to make space for the primary bootstrap and the partition table. The other holes are 0. The type field is the type of the partitition in hexadecimal. The size field is the partition's size in sectors. The + or * may option- ally be added to indicate that the partition must be expanded to contain any leftover space on the device or to mark the partition active. Partitions are padded out to cylinder boundaries, except for the first one, it starts on track 1. Some operating systems care about this. Minix and MS-DOS do not. OPTIONS
-m Minix only, no need to pad partitions. This is the default for subpartition tables. -f Force making a partition table even if the device is too small. EXAMPLE
partition /dev/hd0 01:16384 81:40000 81:2880* 06:20000+ Partitions disk 0 into an 8 Mb DOS partition, 20 Mb Minix /usr, 1.44 Mb Minix / (active), and a DOS partition of at least 10 Mb at the end of the disk. (06:0+ would have been ok too, it's just a sanity check.) SEE ALSO
hd(4), part(8), repartition(8). AUTHOR
Kees J. Bot (kjb@cs.vu.nl) PARTITION(8)
All times are GMT -4. The time now is 10:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy