First of all thank you for your reply, I am on a project of about 150 people, 60 developers, 89 managers and 1 person trying to figure out how to run effectively on an Itanium (me). Sadly, I have the most knowledge of the Itanium architecture, and that is not much.
That being said, I don't run vtlec on the IA64 box because as bad as it runs on the Xeon box, it is worse on the Itaniums. The GUI will come up and core usually about 3 times before it stays up on the Xeon box. On the Itanium it is more like 10 (configuration issue?) I may try again today to get vtlec to run on the itanium to get a better idea of what is going on in the kernel. I was able to use histx to find that for both the CPU_OP_CYCLES and the BE_EXE_BUBBLE.ALL, the culprit is kernel:schedule 20% for both. HMMM
I collected the data for 455 secs which is when the most intense processing is being done, so I believe this is a non-trivial length of time. Which brings me to a question. Since I am in the module view, would'nt the events attributed to "hardware interrupts, daemons being awoken & put back to sleep, etc" be shown on a different thread? When I run top in the individual CPU view I see that I spend a whole lot of time in the sys on the node that I am running main.
As far as processor usage, the simulation framework (SPEEDES) tries to consume 100% of the CPU the entire length of the run, some of this is realtime, some is optimistic and the rest is busy work(GetTimeOfDay and MSG_PEEK). They do this to try to stay ahead of real-time and enforce processor affinity. The frame work also uses shared memory and process forking to allow it to handle larger number of simulation elements. The runs I am looking at are simplified and run on "1" CPU (this is not necessarily true, because we also allow threading)
Sadly, I have to type in data because moving data from our isolated system to one hooked to the internet is not trivial. I have calc and excel on my linux box which helps me statistically prove whether or not something has changed the performance of our sim.
As far as the SA,considering myself lucky is an understatement!
Thanks again, and if I have said something stupid or even mildly wrong please feel free to comment. I would really like to learn this stuff