Hi, > Hello folks, I have an issue where developer wrote a code and it runs 10 > seconds > on his PC, then he moved it to T2000 (16GB RAM, 1.2GHz, 8 CORE, Solaris 10) > and > the same process took 73 seconds. Then he took his code to V240 server (8GB > RAM, > 1GHz, 2CPU's, Solaris 8) and that process completed in around 50 seconds.
Have you considered using some sort of performance analysis on your code ? Sun Studio has excellent tools. http://developers.sun.com/solaris/articles/analyzer_qs.html Gcc uses utility called 'gprof'. Those are the tools especially designed to find performance issues in the code. > We are suspecting that maybe the single Floating-point inside that T2000 is > causing this problem? How would I troubleshoot this problem? Is the application using floating point heavily ? Is it multi-threaded ? > I was thinking to jump into dtrace as everyone is saying its so great Afternoon nap is also great :) > but I am not sure where to start in trying to troubleshoot this. Its > to late for me to go to take dtrace training class at this moment as > it will take weeks for me to get in, and I was looking around on the > internet and there are many different examples but I am not sure which > one would be the right for troubleshooting this issue with T2000. Is the developer machine running also Solaris ? If not, I would recommend finding tool which can be found on both systems, so you can compare results easily (gcc will be probably on both systems) > It does not make sense that two CPU machine that is slower in speed and has > less > RAM outperforms T2000 which has a single CPU but its faster, not only that > its > running Solaris 10 which in theory should be performing better, just does not > make any sense... Less gigahertz does not mean slower machine. T2000 is good at executing multithread, non floating point arithmetic heavy code. > Any suggestions or pointers would be greatly appreciated. Use profiling tools designed for the task. Hope this helps -- Vlad
pgpwm1Bt1KkCZ.pgp
Description: PGP signature
_______________________________________________ dtrace-discuss mailing list [email protected]
