That will be inaccurate because of cache... stuff written to disk just gets shoved into memory until the disk's ready. 30 gigs would probably fill the cache, but still, there's better ways that don't involve waiting for 30 gigs of data to be written.
Linux usually has the hdparm command. It has read tests that take just a few seconds:
There's no equivalent write-speed test but, for a traditional hard disk, read speed and write speed should be about the same.
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)
I analysed disk performance with blktrace and get some data:
read:
8,3 4 2141 2.882115217 3342 Q R 195732187 + 32
8,3 4 2142 2.882116411 3342 G R 195732187 + 32
8,3 4 2144 2.882117647 3342 I R 195732187 + 32
8,3 4 2145 ... (1 Reply)
Hi,
We have smb client running on two of the linux boxes and smb server on another linux system. During a backup operation which uses smb, read of a file was allowed while write to the same file was going on.Also simultaneous writes to the same file were allowed.Following are the settings in the... (1 Reply)
Would simply like to write data (no audio) to a CD/RW disk. The disk drive states CD/RW on the front but don't know for sure if the software is configured to recognize it as a writable disk. I can read/move data from the disk to the hard drive with no issue from the disk. Any help in this... (4 Replies)
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)
Hi,
I went to a computer store and the salesman sold me a SATA cable and told me that all SATA cables are the same. Another salesman at a different store told me a cable rated for SATA 2, which I bought, MIGHT work as well as one rate for SATA 3 but it is not guaranteed. I decided to run a... (3 Replies)
hi all:
as we know , when usb flash disk plug in and aotu mounted , the default permission of the usb flash disk is 700. that means others have no permission . the question: how to make others have read/write permission when the aotu mounted usb flash disk pluge in ? thanks !! (0 Replies)
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)
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
LEARN ABOUT DEBIAN
stressapptest
STRESSAPPTEST(1) General Commands Manual STRESSAPPTEST(1)NAME
stressapptest - stress test application for simulating high load situations
SYNOPSIS
stressapptest [options]
DESCRIPTION
This manual page documents briefly the stressapptest command.
stressapptest (unix name for Stressful Application Test) is a program that tries to maximize randomized traffic to memory from processor
and I/O, with the intent of creating a realistic high load situation in order to test the existing hardware devices in a computer.
OPTIONS
This program supports the following options:
-A Run in degraded mode on incompatible systems.
-C <threads>
Number of memory CPU stress threads to run.
-d <device>
Add a direct write disk thread with block device (or file) 'device'.
-f <filename>
Add a disk thread with tempfile 'filename'.
-F Don't result check each transaction.
-i <threads>
Number of memory invert threads to run.
-l <logfile>
Log output to file 'logfile'.
-m <threads>
Number of memory copy threads to run.
-M <mbytes>
Megabytes of RAM to test.
-n <ipaddr>
Add a network thread connecting to system at 'ipaddr'.
-p <pagesize>
Size in bytes of memory chunks.
-s <seconds>
Number of seconds to run.
-v <level>
Verbosity (0-20), default is 8.
-W Use more CPU-stressful memory copy.
--blocks-per-segment <number>
Number of blocks to read/write per segment per iteration (-d).
--cache-size <size>
Size of disk cache (-d).
--cc_inc_count <number>
Number of times to increment the cacheline's member.
--cc_line_count <number>
Mumber of cache line sized datastructures to allocate for the cache coherency threads to operate.
--cc_test
Do the cache coherency testing.
--destructive
Write/wipe disk partition (-d).
--filesize <size>
Size of disk IO tempfiles.
--findfiles
Find locations to do disk IO automatically.
--force_errors
Inject false errors to test error handling.
--force_errors_like_crazy
Inject a lot of false errors to test error handling.
--listen
Run threads that listen for incoming net connections.
--local_numa
Choose memory regions associated with each CPU to be tested by that CPU.
--max_errors <number>
Exit early after finding specified number of errors.
--monitor_mode
Only do ECC error polling, no stress load.
--no_errors
Run without checking for ECC or other errors.
--paddr_base <address>
Allocate memory starting from this address.
--pause_delay <seconds>
Delay (in seconds) between power spikes.
--pause_duration <seconds>
Duration (in seconds) of each pause.
--random-threads <number>
Number of random threads for each disk write thread (-d).
--read-block-size <size>
Size of block for reading (-d).
--read-threshold <time>
Maximum time (in us) a block read should take (-d).
--remote_numa <time>
Choose memory regions not associated with each CPU to be tested by that CPU.
--segment-size <size>
Size of segments to split disk into (-d).
--stop_on_errors
Stop after finding the first error.
--write-block-size <size>
Size of block for writing (-d). If not defined, the size of block for writing will be defined as the size of block for reading.
--write-threshold <time>
Maximum time (in us) a block write should take (-d).
SEE ALSO
http://code.google.com/p/stressapptest/
AUTHOR
stressapptest was written by Nick Sanders and Rapahel Menderico (Google Inc).
This manual page was written by Michael Prokop <mika@debian.org> for the Debian project (and may be used by others).
2009-10-20 STRESSAPPTEST(1)