Johnny Gonzalez L. wrote:

yep, I was thinking in doing a top while issuing one of my new batch tests to try to catch where is the bigger delay, to see if it is in disk writting, db access, etc.

maybe it would be a good idea to insert some:
"time" or "times" commands at certain places this will give a bit more detailed information for each programm you call with it ;)
but i don't know if its available at your system

so maybe its usefull to call some commands with this too...
will be more accurate then top i guess - hehe

greetings
dalini


NAME
      time - time a simple command or give resource usage

SYNOPSIS
      time [options] command [arguments...]

DESCRIPTION
The time command runs the specified program command with the given arguments. When command finishes, time writes a message to standard output giving timing statistics about this program run. These statis- tics consist of (i) the elapsed real time between invocation and termi- nation, (ii) the user CPU time (the sum of the tms_utime and tms_cutime values in a struct tms as returned by times(2)), and (iii) the system CPU time (the sum of the tms_stime and tms_cstime values in a struct
      tms as returned by times(2)).

----------------------

NAME
      times - write process times

SYNOPSIS
      times

DESCRIPTION
The times utility shall write the accumulated user and system times for the shell and for all of its child processes, in the following POSIX
      locale format:


             "%dm%fs %dm%fs\n%dm%fs %dm%fs\n", <shell user minutes>,
                 <shell user seconds>, <shell system minutes>,
                 <shell system seconds>, <children user minutes>,
                 <children user seconds>, <children system minutes>,
                 <children system seconds>

The four pairs of times shall correspond to the members of the <sys/times.h> tms structure (defined in the Base Definitions volume of IEEE Std 1003.1-2001, Chapter 13, Headers) as returned by times():
      tms_utime, tms_stime, tms_cutime, and tms_cstime, respectively.



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Openca-Users mailing list
Openca-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openca-users

Reply via email to