Sponsored Content
Full Discussion: Svhptdaemon
Operating Systems HP-UX Svhptdaemon Post 302989054 by bbbngowc on Friday 6th of January 2017 02:03:47 PM
Old 01-06-2017
Quote:
Originally Posted by jim mcnamara
How do you attribute the 50% sys usage to that one process? That is for all processes is it not? BTW - when ANY process runs it spends time in kernel code (sys) when invoking a syscall, .e.g. open(). That means vmstat and sar would normally show a summed % sys for all processes system wide.

Doesn't mean that the daemon is or is not using most of that %.
My mistake. I was trying to say the same thing you just did. The usage is around 50%.
 
serialize(2)							System Calls Manual						      serialize(2)

NAME
serialize() - force target process to run serially with other processes SYNOPSIS
DESCRIPTION
The system call is used to force the target process referenced by the pid value passed in to run serially with other processes also marked for serialization. If the value of pid is zero, then the currently running process is marked for serialization. Once a process has been marked by the process stays marked until process completion, unless is reissued on the serialized process with timeshare set to 1. If timeshare is set to 1, the process specified in pid will be returned to normal timeshare scheduling algorithms. This call is used to improve process throughput since process throughput usually increases for large processes when they are executed seri- ally instead of allowing each program to run for only a short period of time. By running large processes one at a time, the system makes more efficient use of the CPU as well as system memory, since each process does not end up constantly faulting in its working set, to only have the pages stolen when another process starts running. As long as there is enough memory in the system, processes marked by behave no differently from other processes in the system. However, once memory becomes tight, processes marked by are run one at a time with the highest priority processes being run first. Each process runs for a finite interval of time before another serialized process is allowed to run. RETURN VALUE
returns zero upon successful completion, or nonzero if the system call failed. ERRORS
If fails, it sets (see errno(2)) to the following value: The pid passed in does not exist. WARNINGS
The user has no way of forcing an execution order on serialized processes. AUTHOR
was developed by HP. SEE ALSO
serialize(1), privileges(5). serialize(2)
All times are GMT -4. The time now is 01:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy