Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory data from blktrace: read speed V.S. write speed Post 302365199 by achenle on Monday 26th of October 2009 09:42:31 AM
Old 10-26-2009
The write operations are almost certainly getting cached somewhere, most likely in the kernel page cache or the cache on the disk(s) themselves depending on your OS and hardware setup.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Speed it up!

I wonder, are there any "tricks" to increase my server's access time in general? (4 Replies)
Discussion started by: pappous
4 Replies

2. UNIX for Dummies Questions & Answers

Speed of mv vs. cp

Hi, Is mv (move) command quicker than cp (copy command)? I have large files and I want to know if mv actually copy the data to a new file then deletes the old or whether it just alters information the file system without physically moving data - Unfortuanately I don't have large files to test... (2 Replies)
Discussion started by: GMMike
2 Replies

3. Filesystems, Disks and Memory

dmidecode, RAM speed = "Current Speed: Unknown"

Hello, I have a Supermicro server with a P4SCI mother board running Debian Sarge 3.1. This is the "dmidecode" output related to RAM info: RAM speed information is incomplete.. "Current Speed: Unknown", is there anyway/soft to get the speed of installed RAM modules? thanks!! Regards :)... (0 Replies)
Discussion started by: Santi
0 Replies

4. Filesystems, Disks and Memory

Write Speed into a big file (in Gb's)

If a file size increases in Linux/UNIX to say in GB's then will there be a decrease in write speed. I mean will it take more time to write to a large file then to a small one?? Please clarify? Thanks in advance (2 Replies)
Discussion started by: anilgurwara
2 Replies

5. Shell Programming and Scripting

How to speed up grep?

hi i'm greping the files with sepefic keyword, where the file is of too big. Assume there are 10 days log file each of more than 200mb. i've to grep all those files with a specific keywords. for example, 1. i'll grep for error message 2. after the i'll do one more grep for keyword... (4 Replies)
Discussion started by: vij_krr
4 Replies

6. Filesystems, Disks and Memory

Disk read and write speed.

Being a novice user to linux i m little unaware of how would i check disk read write speed. One of my mate is suggesting to create a file using dd command and check how much time it takes to create a 30 gb file . I think this has a little sense however i would also like to take your reviews... (5 Replies)
Discussion started by: pinga123
5 Replies

7. Hardware

Hardware Correction: How to change DVD write speed

I am now on Kernel 2.6.32-26 For me 16x CD write speed is okay. I have old hardware which was able to write DVDs at 1x, back in previous linux version. Now, I dont get speed of less than 4x. Tested on k3b, xfburn, and brasero. But all start at bottom 4x write speed. k3b forced back to... (0 Replies)
Discussion started by: makh
0 Replies

8. Shell Programming and Scripting

Speed Up Grep

Hi, I have to grep string from 20 - 30 files each carries 200 - 300 MB size and append to the file. How to speed the grepping time. cat catalina.out_2012_01_01 | grep "xxxxx" >> backup.txt PLZ, Suggest me, Regards, Nanthagopal A (5 Replies)
Discussion started by: nanthagopal
5 Replies

9. Red Hat

Read speed too bad on NAS share on VM

Hi, We have two servers in scenario (vmsoldot01 is Oracle VM with Linux and tldtppod15 is physical Linux server). One NAS share is mounted on both servers with similar permissions and access. But READ speed is too bad on virtual in comparison to physical server. While trying to diagnose this, I... (2 Replies)
Discussion started by: solaris_1977
2 Replies

10. UNIX for Advanced & Expert Users

How to read a fast written log file at Real time speed?

Hello All, I am building a real time parser for a log file in my application. The log file is continuously written at a very fast pace and gets rolled over every 10 minutes. I have measured the speed and observed that around 1000 lines are written to it every second, each line about 30-40... (7 Replies)
Discussion started by: cool.aquarian
7 Replies
BTREPLAY(8)															       BTREPLAY(8)

NAME
btreplay - recreate IO loads recorded by blktrace SYNOPSIS
btreplay [ options ] <dev...> DESCRIPTION
The btrecord and btreplay tools provide the ability to record and replay IOs captured by the blktrace utility. Attempts are made to main- tain ordering, CPU mappings and time-separation of IOs. The blktrace utility provides the ability to collect detailed traces from the kernel for each IO processed by the block IO layer. The traces provide a complete timeline for each IO processed, including detailed information concerning when an IO was first received by the block IO layer -- indicating the device, CPU number, time stamp, IO direction, sector number and IO size (number of sectors). Using this information, one is able to replay the IO again on the same machine or another set up entirely. The basic operating work-flow to replay IOs would be something like: - Run blktrace to collect traces. Here you specify the device or devices that you wish to trace and later replay IOs upon. Note: the only traces you are interested in are QUEUE requests -- thus, to save system resources (including storage for traces), one could specify the -a queue command line option to blktrace. - While blktrace is running, you run the workload that you are interested in. - When the work load has completed, you stop the blktrace utility (thus saving all traces over the complete workload). - You extract the pertinent IO information from the traces saved by blktrace using the btrecord utility. This will parse each trace file created by blktrace, and crafty IO descriptions to be used in the next phase of the workload processing. - Once btrecord has successfully created a series of data files to be processed, you can run the btreplay utility which attempts to generate the same IOs seen during the sample workload phase. OPTIONS
-c <num> --cpus=<num> Set number of CPUs to use. -d <dir> --input-directory=<dir> Set input directory. This option requires a single parameter providing the directory name for where input files are to be found. The default directory is the current directory (.). -F --find-records Find record files automatically This option instructs btreplay to go find all the record files in the directory specified (either via the -d option, or in the default directory (.). -h --help Show help and exit. -i <basename> --input-base=<basename> Set base name for input files. Each input file has 3 fields: 1. Device identifier (taken directly from the device name of the blktrace output file). 2. btrecord base name -- by default ``replay''. 3. The CPU number (again, taken directly from the blktrace output file name). This option requires a single parameter that will override the default name (replay), and replace it with the specified value. -I <num> --iterations=<num> Set number of iterations to run. This option requires a single parameter which specifies the number of times to run through the input files. The default value is 1 -M <filename> --map-devs=<filename> Specify device mappings. This option requires a single parameter which specifies the name of a file contain device mappings. The file must be very simply managed, with just two pieces of data per line: - The device name on the recorded system (with the '/dev/' removed). Example: /dev/sda would just be sda. - The device name on the replay system to use (again, without the '/dev/' path prepended). An example file for when one would map devices /dev/sda and /dev/sdb on the recorded system to dev/sdg and sdh on the replay system would be: sda sdg sdb sdh The only entries in the file that are allowed are these two element lines -- we do not (yet?) support the notion of blank lines, or comment lines, or the like. The utility allows for multiple -M options to be supplied on the command line. -N --no-stalls Disable pre-bunch stalls. When specified on the command line, all pre-bunch stall indicators will be ignored. IOs will be replayed without inter-bunch delays. -x <factor> --acc-factor=<factor> Specify acceleration factor. Default value is 1 (no acceleration). -v --verbose Enable verbose output. When specified on the command line, this option instructs btreplay to store information concerning each stall and IO operation performed by btreplay. The name of each file so created will be the input file name used with an extension of .rep appended onto it. Thus, an input file of the name sdab.replay.3 would generate a verbose output file with the name sdab.replay.3.rep in the directory specified for input files. In addition, btreplay will also output to stderr the names of the input files being processed. -V --version Show version number and exit. -W --write-enable Enable writing during replay. As a precautionary measure, by default btreplay will not process write requests. In order to enable btreplay to actually write to devices one must explicitly specify the -W option. AUTHORS
btreplay was written by Alan D. Brunelle. This man page was created from the btreplay documentation by Bas Zoetekouw. REPORTING BUGS
Report bugs to <linux-btrace@vger.kernel.org> COPYRIGHT
Copyright (C) 2007 Alan D. Brunelle, Alan D. Brunelle and Nathan Scott. This is free software. You may redistribute copies of it under the terms of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. This manual page was created for Debian by Bas Zoetekouw. It was derived from the documentation provided by the authors and it may be used, distributed and modified under the terms of the GNU General Public License, version 2. On Debian systems, the text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-2. SEE ALSO
The full documentation for btreplay can be found in /usr/share/doc/blktrace on Debian systems. blktrace (8), blkparse (1), btrecord (8) blktrace git-20071207142532 December 8, 2007 BTREPLAY(8)
All times are GMT -4. The time now is 11:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy