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:
results from new system:
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?
The msec/call number is awfully small to start with - and it doesn't change. How are you timing each function call? To what precision? You may be running fast enough on the new server that your measurement isn't precise enough and your code keeps adding zero time for each execution.
I don't think it's the SMP that's causing the problem, at least not directly.
Thanks for your input. To answer your questions how am I timing and to what precision - I just compiled the app with -p flag. Then I run the app through the test routine, which created the mon.out file. Then I run prof app-name and that gives me results I show. I don't think I can control precision of the output.
As far as new machine being much faster than the old one - yes, the app runs roughly twice faster on this new h/w. But definitely not 10 times faster.
Can you disable CPUs and/or hyperthreading as necessary via BIOS settings on your new hardware to limit the OS to only one CPU thread? That seems to me to be a really easy test to run that will provide good information.
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)
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)
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)
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)
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)
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)
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)