08-31-2006
The simple answer is to create a test dummy directory on a local disk and run the app against local devices. If iostat is what you want.
Does your box have nfsstat? However iostat & nfsstat tell you about a subsystem(s), not necessarily what one executable is doing.
profiling an app gives you real data for just what the app is doing, and eliminates everybody else. IT may be worth looking at.
7 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
Hi,
on a linux server I have the following :
vmstat 2 10
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 4 0 675236 39836 206060 1617660 3 3 3 6 8 7 1 1 ... (1 Reply)
Discussion started by: big123456
1 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. UNIX for Dummies Questions & Answers
hi I am having a performance issue with the following requirement
i have to create a permutation and combination on a set of three files
such that each record in each file is picked and the output is redirected in
a specific format but it is taking around 70 odd hours to prepare a
combination... (7 Replies)
Discussion started by: mad_man12
7 Replies
Mojo(3pm) User Contributed Perl Documentation Mojo(3pm)
NAME
Mojo - Duct tape for the HTML5 web!
SYNOPSIS
use Mojo::Base 'Mojo';
# All the complexities of CGI, PSGI, HTTP and WebSockets get reduced to a
# single method call!
sub handler {
my ($self, $tx) = @_;
# Request
my $method = $tx->req->method;
my $path = $tx->req->url->path;
# Response
$tx->res->code(200);
$tx->res->headers->content_type('text/plain');
$tx->res->body("$method request for $path!");
# Resume transaction
$tx->resume;
}
DESCRIPTION
Mojo provides a flexible runtime environment for Perl real-time web frameworks. It provides all the basic tools and helpers needed to write
simple web applications and higher level web frameworks such as Mojolicious.
See Mojolicious for more!
ATTRIBUTES
Mojo implements the following attributes.
"home"
my $home = $app->home;
$app = $app->home(Mojo::Home->new);
The home directory of your application, defaults to a Mojo::Home object which stringifies to the actual path.
# Generate portable path relative to home directory
my $path = $app->home->rel_file('data/important.txt');
"log"
my $log = $app->log;
$app = $app->log(Mojo::Log->new);
The logging layer of your application, defaults to a Mojo::Log object.
# Log debug message
$app->log->debug('It works!');
"ua"
my $ua = $app->ua;
$app = $app->ua(Mojo::UserAgent->new);
A full featured HTTP 1.1 user agent for use in your applications, defaults to a Mojo::UserAgent object. Note that this user agent should
not be used in plugins, since non-blocking requests that are already in progress will interfere with new blocking ones.
# Perform blocking request
my $body = $app->ua->get('mojolicio.us')->res->body;
METHODS
Mojo inherits all methods from Mojo::Base and implements the following new ones.
"new"
my $app = Mojo->new;
Construct a new Mojo application. Will automatically detect your home directory and set up logging to "log/mojo.log" if there's a "log"
directory.
"build_tx"
my $tx = $app->build_tx;
Transaction builder, defaults to building a Mojo::Transaction::HTTP object.
"config"
my $config = $app->config;
my $foo = $app->config('foo');
$app = $app->config({foo => 'bar'});
$app = $app->config(foo => 'bar');
Application configuration.
# Manipulate configuration
$app->config->{foo} = 'bar';
my $foo = $app->config->{foo};
delete $app->config->{foo};
"handler"
$app->handler($tx);
The handler is the main entry point to your application or framework and will be called for each new transaction, which will usually be a
Mojo::Transaction::HTTP or Mojo::Transaction::WebSocket object. Meant to be overloaded in a subclass.
sub handler {
my ($self, $tx) = @_;
...
}
SEE ALSO
Mojolicious, Mojolicious::Guides, <http://mojolicio.us>.
perl v5.14.2 2012-09-05 Mojo(3pm)