09-14-2018
It looks to me that you want to be able to measure performance, probably by transaction request/return times. Documentum originally worked on files of almost any kind. So your asking for "file" times is confusing everyone. They think you mean UNIX file access times. I am guessing this is sort of a communication breakdown here
Documentum seemed like Ingres (or Oracle) for any kind of digital object - files, metafiles, metadata. To me anyway. If this helps people to answer the question.
I do not know anything much about Documentum now. What performance monitoring tools come with the product? Use them to generate data. We can help you organize and use that data to answer the requirements.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all,
If I give ls , it lists files in 1 second.
It I give ls -l , it takes 8 seconds
There are only 55 files in the directory.
Any explanation?
Thanks
Wilson (4 Replies)
Discussion started by: geraldwilson
4 Replies
2. UNIX for Advanced & Expert Users
I am experiencing a problem where under a dial condition I am experiencing packet loss, which is failrly normal, but the response to the packet loss is taking bewteen 6 and 10 seconds. Could someone please advise what the industry standard is on the response time under a packet loss senario. (1 Reply)
Discussion started by: shane
1 Replies
3. UNIX for Advanced & Expert Users
in HP-UX how i can measure the response time
and how can i find the maximum IO (1 Reply)
Discussion started by: salhoub
1 Replies
4. Shell Programming and Scripting
Hi ,
Please help me
shell script to determine the active processes on the system which are running since long time (2 Replies)
Discussion started by: itian2010
2 Replies
5. Shell Programming and Scripting
I have a running log file (jboss_server.log) which rotates at midnight . I need to constantly check and calculate the time for each thread and alert if it doesnt complete within 60 minute. For example my log file has following printed .
I want to run a script in cron every 30 minutes and... (2 Replies)
Discussion started by: gubbu
2 Replies
6. IP Networking
Hi everyone!
How can I get response time difference between GET and HTTP/1.0 200 OK (i mean time latency of web-server) with using of tshark&shell or something else for each hostname from pcap file?
What can you recommend me to do that? (1 Reply)
Discussion started by: lepetal
1 Replies
7. Shell Programming and Scripting
Hi,
I am trying to calculate avg response time on hourly basis from the log file which has millions of records.
As of now I am trying with creating temp file which will have lines with unique id and start time and end time and after that another script will run on this temp file to... (7 Replies)
Discussion started by: random_thoughts
7 Replies
8. Shell Programming and Scripting
Hi,
My goal is to monitor the response time from the access logs of nginx server. I am using gawk to print the needed fields - 'response time' and 'name of the service' from nginx logs.
Command: gawk '($6 ~ /cloudservice/) {print $10, $6}' access.log
Output:
0.645 /nc/cloudservice... (6 Replies)
Discussion started by: nshah11
6 Replies
9. Shell Programming and Scripting
so i've been using this a lot in a lot of my scripts:
( columnA & columnAPID=$! & columnB & columnBPID=$! & columnC & columnCPID=$! &) &
wait ${columnAPID}
wait ${columnBPID}
wait ${columnCPID}
It seems to work as ive seen it dramatically reduce run time of my scripts.
however, i'm... (5 Replies)
Discussion started by: SkySmart
5 Replies
10. UNIX for Beginners Questions & Answers
Hello everybody ,
I launched cron to execute a task every hour but the job takes more than hour that's why I'm getting more than 1000 cron processes running at the same time !!!
My question is how to tell cron not to execute unless the job terminated in order to have only one process running .... (14 Replies)
Discussion started by: beautymind
14 Replies
LEARN ABOUT REDHAT
pthread_mutexattr_init
PTHREAD_MUTEXATTR(3) Library Functions Manual PTHREAD_MUTEXATTR(3)
NAME
pthread_mutexattr_init, pthread_mutexattr_destroy, pthread_mutexattr_settype, pthread_mutexattr_gettype - mutex creation attributes
SYNOPSIS
#include <pthread.h>
int pthread_mutexattr_init(pthread_mutexattr_t *attr);
int pthread_mutexattr_destroy(pthread_mutexattr_t *attr);
int pthread_mutexattr_settype(pthread_mutexattr_t *attr, int kind);
int pthread_mutexattr_gettype(const pthread_mutexattr_t *attr, int *kind);
DESCRIPTION
Mutex attributes can be specified at mutex creation time, by passing a mutex attribute object as second argument to pthread_mutex_init(3).
Passing NULL is equivalent to passing a mutex attribute object with all attributes set to their default values.
pthread_mutexattr_init initializes the mutex attribute object attr and fills it with default values for the attributes.
pthread_mutexattr_destroy destroys a mutex attribute object, which must not be reused until it is reinitialized. pthread_mutexattr_destroy
does nothing in the LinuxThreads implementation.
LinuxThreads supports only one mutex attribute: the mutex kind, which is either PTHREAD_MUTEX_FAST_NP for ``fast'' mutexes,
PTHREAD_MUTEX_RECURSIVE_NP for ``recursive'' mutexes, or PTHREAD_MUTEX_ERRORCHECK_NP for ``error checking'' mutexes. As the NP suffix
indicates, this is a non-portable extension to the POSIX standard and should not be employed in portable programs.
The mutex kind determines what happens if a thread attempts to lock a mutex it already owns with pthread_mutex_lock(3). If the mutex is of
the ``fast'' kind, pthread_mutex_lock(3) simply suspends the calling thread forever. If the mutex is of the ``error checking'' kind,
pthread_mutex_lock(3) returns immediately with the error code EDEADLK. If the mutex is of the ``recursive'' kind, the call to
pthread_mutex_lock(3) returns immediately with a success return code. The number of times the thread owning the mutex has locked it is
recorded in the mutex. The owning thread must call pthread_mutex_unlock(3) the same number of times before the mutex returns to the
unlocked state.
The default mutex kind is ``fast'', that is, PTHREAD_MUTEX_FAST_NP.
pthread_mutexattr_settype sets the mutex kind attribute in attr to the value specified by kind.
pthread_mutexattr_gettype retrieves the current value of the mutex kind attribute in attr and stores it in the location pointed to by kind.
RETURN VALUE
pthread_mutexattr_init, pthread_mutexattr_destroy and pthread_mutexattr_gettype always return 0.
pthread_mutexattr_settype returns 0 on success and a non-zero error code on error.
ERRORS
On error, pthread_mutexattr_settype returns the following error code:
EINVAL kind is neither PTHREAD_MUTEX_FAST_NP nor PTHREAD_MUTEX_RECURSIVE_NP nor PTHREAD_MUTEX_ERRORCHECK_NP
AUTHOR
Xavier Leroy <Xavier.Leroy@inria.fr>
SEE ALSO
pthread_mutex_init(3), pthread_mutex_lock(3), pthread_mutex_unlock(3).
LinuxThreads PTHREAD_MUTEXATTR(3)