03-11-2008
A totally different perspective
Could it be the first time you tried to edit the file you read if from disk an the second time it was in cache so there was no I/O? It will take a couple of seconds to read a 100MB file off disk.
If this is something you've never paid any attention to before you should run a tool like collectl -
SourceForge.net: collectl which can show you what's going on even at the sub-second level on your system. It's amazing how ofter people just look at how long an operation takes to perform vs what the system is doing. With collectl you'll also be able to watch the cpu and memory during your tests...
-mark
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
i have changed a slow server with Solaris 7 to a bigger one with
Solaris 8 (Sun Ultra 2). Now i have a real bad performance
problem (only CPU).
Solaris 7 ran with standard FTP and Samba 2.0.7.
The new machine is running ProFTP and Samba 2.0.9.
There are a lot of NFS Shares and... (5 Replies)
Discussion started by: olso
5 Replies
2. UNIX for Advanced & Expert Users
Hi,
1-in vmstat commande line, in reply, which column is the more important to look and verify if server is very slow ?
2-how can I see how many sessions are opened with the same login ?
Many thanks before. (2 Replies)
Discussion started by: big123456
2 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have this on a AIX UNIX machine :
ps aux| head -20
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 23.7 0.0 12 15808 - A 19:38:15 903:13 wait
root 774 23.7 0.0 12 15808 - A 19:38:15 902:13 wait
root 1290 23.6 0.0 ... (2 Replies)
Discussion started by: big123456
2 Replies
4. UNIX for Advanced & Expert Users
i want to determine I/O performance of an
executable,
but iostat dont give correct results because
the disk that i am writing to and reading from,
are not physical disk of the host machine,
instead of these local disks we are using
a network storage.
is there any standard way in unix to get... (2 Replies)
Discussion started by: gfhgfnhhn
2 Replies
5. News, Links, Events and Announcements
About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in... (0 Replies)
Discussion started by: MarkSeger
0 Replies
6. Solaris
Hi all,
I have two storadge 3510 Fc .. with 12 disks 146Gb ..total 1752Gb each storadge. I need to use about 1.4 Tb of it. and want RAID1 ..
I need 13 mount points ..
So question:
for best performance and redundjancy how I must do it.
create 13 logical drives on each stordge with same size... (1 Reply)
Discussion started by: samar
1 Replies
7. Shell Programming and Scripting
I'm using sed to do find and replace. But since the file is huge and i have more than 1000 files to be searched, the script is taking a lot of time. Can somebody help me with a better sed command. Below is the details.
Input:
1
1
2
3
3
4
5
5
Here I know the file is sorted.
... (4 Replies)
Discussion started by: gpaulose
4 Replies
8. Shell Programming and Scripting
I'm searching the most effective way of doing the following task, so if someone can either provide a working solution with sed or one totally different but more effective then what I've got so far then please go ahead!
The debugme directory has 3 subdirectorys and each of them has one .txt file... (7 Replies)
Discussion started by: TehOne
7 Replies
9. UNIX for Dummies Questions & Answers
Hi Guys,
I've wondered for some time the performance analysis between using sed and awk. say i want to print lines from a very large file. For ex say a file with 100,000 records. i want to print the lines 25,000 to 26,000 i can do so by the following commands:
sed -n '25000,26000 p'... (11 Replies)
Discussion started by: Irishboy24
11 Replies
fixnt(1) Debian fixnt(1)
NAME
fixnt - Filter for the Windows NT postscript printer driver.
SYNOPSIS
fixnt < BADFILE.ps > GOODFILE.ps
DESCRIPTION
The Windows NT postscript driver has a tendency to make broken postscript files, that are incompatible with psutils. fixnt is a filter
that fixes these problems, allowing the use of psnup(1).
The filter takes the broken postscript file on stdin, and outputs a fixed postscript file on stdout. It has no other form for invocation
and takes no options on the command-line.
OPTIONS
fixnt takes no options.
BUGS
fixnt does not check for NTPSOct94. For a workaround, use a sed(1) command to replace 'NTPSOct94' with 'NTPSOct95', like so:
sed 's/NTPSOct94/NTPSOct95/g'
This is particularly important for Windows NT 3.5 users.
AUTHOR
fixnt was written by Holger Bauer <Holger.Bauer@topmail.de>, Michael Rath <rath@itsm.uni-stuttgart.de>, and Akim Demaille
<demaille@inf.enst.fr>.
REPORTING BUGS
Report bugs to the Authors, but avoid sending large postscript files.
Patches are always welcome; send to <bauer@itsm.uni-stuttgart.de>.
SEE ALSO
psnup(1), sed(1)
a2ps February 2003 fixnt(1)