Sponsored Content
Full Discussion: Profiling results and SMP
Top Forums Programming Profiling results and SMP Post 302904555 by migurus on Wednesday 4th of June 2014 05:16:40 PM
Old 06-04-2014
Profiling results and SMP

The SCO OSR 5.7 system was migrated from older HP DL360 to new DL380 G7. The SMP feature was not activated on older box, it is activated now on this 4 core Xeon.

A s/w we maintain has been copied without any change over to the new box. I noticed that the application profiling does not show any Seconds and Cumulative seconds for our functions.

results from old system:
Code:
 %Time Seconds Cumsecs  #Calls   msec/call  Name
   3.8    0.32    4.21 4464168      0.0001  my_func1
   3.5    0.30    4.51 4315824      0.0001  my_func2
   3.4    0.29    4.80 1973552      0.0001  my_func4

results from new system:
Code:
 %Time Seconds Cumsecs  #Calls   msec/call  Name
   0.0    0.00    0.00 4464168      0.0001  my_func1
   0.0    0.00    0.00 4315824      0.0001  my_func2
   0.0    0.00    0.00 1973552      0.0001  my_func4

One more note: the last line on the prof output in Cumsecs in the old system would show pretty much the time it took to execute, on the new system it shows a number roughly ten times smaller than actual execution time.


It is static COEFF binary built with the same make file with same compiler, nothing changed between old and new environment, except SMP. The system (old and new) is pretty much one user system idle 99.9% of the time.

I guess the SMP feature is the reason for the skewed profiling. Does anybody know about this issue? Any ideas?

Thanks in advance.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SMP support in Linux 7.3

What is the SMP support like when you are running Linux 7.3 on a system with 2-4 CPUs? (3 Replies)
Discussion started by: AngryRabbi
3 Replies

2. SCO

SCO unix 5.0.7 (SMP)

I have a dell machine Dell 2600 PowerEdge it has two processor (intel Xeon ). Is there a path or a software that will work with SCO unix in order to enable second processor and how would i know that the second processor is active. Thanks a lot guys . (1 Reply)
Discussion started by: josramon
1 Replies

3. Linux Benchmarks

Dual Intel Xeon 2.4Ghz - Linux 2.4.26 SMP

System: CPU/Speed: Dual Intel Xeon 2.4Ghz Ram: 2 GB DDR 266 SDRAM Motherboard: SuperMicro X5DE8-GG Bus: 533MHz/400MHz system bus - Cache: 512KB HD Controller: EIDE Serverworks™ GC-SL Chipset Extra GCC compiler flags: -s... (3 Replies)
Discussion started by: Neo
3 Replies

4. Red Hat

full shutdown in smp

I have installed redhat linux 9.0 on P4 HT machine. The grub boot loader shows path to smp mode and normal mode. when machine shut downs from smp version kernal , need to press the power button to power off. But in normal mode the system shut downs or power downs automatically(ie, full... (2 Replies)
Discussion started by: pcsaji
2 Replies

5. Programming

socket close() -w- pthreads linux 2.6.18.2-34 (suse) SMP

Interesting issue. There was some discussion on the LKML last year regarding the potential problems in concurrent applications reusing file descriptors in various scenarios. The main issue is that the reuse of a file descriptor and reception of data in a threaded application can be confused pretty... (1 Reply)
Discussion started by: ramen_noodle
1 Replies

6. UNIX for Advanced & Expert Users

Kernel Profiling

I compiled my device driver with the profiling option -p but while linking I am getting undefined reference to _mcount. LD /vobs/femto_drivers/DspBiosLink/dsplinkk/src/dsplinkk.o Building modules, stage 2. MODPOST *** Warning: "_mcount" undefined! Architechture: ppc32 From... (0 Replies)
Discussion started by: Ashok V
0 Replies

7. High Performance Computing

MPI + Cluster SMP

Hola, he instalado mpich2 vs. 1.2.1p1 en un cluster de biprocesadores con las opciones por defecto (antes usaba ssm pero visto que se quedaba colgado, lo he dejado con nemesis). El caso es que quisiera que cada vez que lanzo un job (por ejemplo de 2 procesos), cada proceso del trabajo se fuera... (1 Reply)
Discussion started by: Sonia_
1 Replies

8. UNIX for Dummies Questions & Answers

profiling execution of a process

question goes like this : Explain how users can profile execution of a process with help of an example? can some one pls give me the answer?? (1 Reply)
Discussion started by: rakesh1988
1 Replies

9. AIX

C profiling tool for AIX

Hello everybody, Please let me know if there are any free C profiling tool for AIX environment Thanks in advance (0 Replies)
Discussion started by: SteAlma
0 Replies

10. Debian

Profiling Processes while shutdown

I was wondering how can I find the culprit of a slow shutdown on my debian box? I am actually looking for a diagnosis tool that might dump the process name and amount of time it took to close the process after signal was send. As for now I am trying to use journalctl to seek some information,... (5 Replies)
Discussion started by: Varun Pandey
5 Replies
SMP_REP_GENERAL(8)						     SMP_UTILS							SMP_REP_GENERAL(8)

NAME
smp_rep_general - invoke REPORT GENERAL SMP function SYNOPSIS
smp_rep_general [--brief] [--changecount] [--help] [--hex] [--interface=PARAMS] [--raw] [--sa=SAS_ADDR] [--verbose] [--version] [--zero] SMP_DEVICE[,N] DESCRIPTION
Sends a SAS Management Protocol (SMP) REPORT GENERAL function request to a SMP target. The SMP target is identified by the SMP_DEVICE and the SAS_ADDR. Depending on the interface, the SAS_ADDR may be deduced from the SMP_DEVICE. The mpt interface uses SMP_DEVICE to identify a HBA (an SMP initiator) and needs the additional ,N to differentiate between HBAs if there are multiple present. OPTIONS
Mandatory arguments to long options are mandatory for short options as well. -b, --brief reports (prints to stdout) only a few important fields from the response. -c, --changecount reports (prints to stdout) the value of the expander change count field from the response. The value is printed in decimal and is in the range 0 to 65535. Only expanders compliant with SAS-1.1 (and earlier) should yield 0. [Expanders compliant with SAS-2 (and later) should set the "long response" bit in the REPORT GENERAL response to 1.] -h, --help output the usage message then exit. -H, --hex output the response (less the CRC field) in hexadecimal. -I, --interface=PARAMS interface specific parameters. In this case "interface" refers to the path through the operating system to the SMP initiator. See the smp_utils man page for more information. -r, --raw send the response (less the CRC field) to stdout in binary. All error messages are sent to stderr. -s, --sa=SAS_ADDR specifies the SAS address of the SMP target device. Typically this is an expander. This option may not be needed if the SMP_DEVICE has the target's SAS address within it. The SAS_ADDR is in decimal but most SAS addresses are shown in hexadecimal. To give a number in hexadecimal either prefix it with '0x' or put a trailing 'h' on it. -v, --verbose increase the verbosity of the output. Can be used multiple times -V, --version print the version string and then exit. -z, --zero zero the Allocated Response Length field in the request. This is required for strict SAS-1.1 compliance. However this option should not be given in SAS-2 and later; if it is given an abridged response may result. EXAMPLES
See "Examples" section in http://sg.danny.cz/sg/smp_utils.html CONFORMING TO
The SMP REPORT GENERAL function was introduced in SAS-1, with small additions in SAS-1.1 . There have been a large number of additions in SAS-2 . AUTHORS
Written by Douglas Gilbert. REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>. COPYRIGHT
Copyright (C) 2006-2011 Douglas Gilbert This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. SEE ALSO
smp_utils, smp_discover(smp_utils) smp_utils-0.96 May 2011 SMP_REP_GENERAL(8)
All times are GMT -4. The time now is 06:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy