I have downloaded trial of VTune 9.0 update 7 to re-evaluate VTune for our company. After installing EM64T version on XP x64 SP2 I tried to profile a project. Problems I encountered are as follows:
About that SSE_Scalar_Instructions_Not_Fused code example:
movss xmm6, dword ptr [ebp + 24h] ! shufps xmm6, xmm6, 0 ; SSE_Scalar_Instructions_Not_Fused ... label: test edx, edx jz done ... sub edx, 1 ! jmp label ; SSE_Scalar_Instructions_Not_Fused done:
I sincerely doubt I could replace movss/shufps with x87 code much less that jmp and integer instructions.
I have attached screenshots of Task Manager CPU load graph, process list and memory load for devenv.exe when launched by double-clicking on a .sln file and from the Start Menu shortcut as described above.
Someone from Intel argued with me last time and said I was just bashing VTune without presenting real arguments. If we released and sold such a buggy application for our company (we deal wit h medical imaging) we would already have our heads chopped off and thrown to lions. It looks like VTune is indeed developed in someone's spare time as a fun project.
In my opinion usability is on a level of a small child's toy and it also evokes the proper emotions — to smash it into the nearest wall when it doesn't fit nicely with other "toys" and it doesn't do what you expect from it. My advice would be to either fix it quickly or start giving it away for free.
Finally, I am really frustrated with this experience and the lack of progress in VTune development. Seems that Avery Lee (author of VirtualDub) was right when he said that the last usable VTune was version 6.1.
Frankly speaking, VTune Tuning Assistant annoys me either, although I know the reasons of its behavior and I do not bother with this feature. Yes, Tuning Assistant component experiences lack of support and in some cases is useless of gives weird advises. In your case Id recommend drop it, since you seem to be quite experienced in low level optimization. Rely mostly on the microprocessor optimization reference manual and CPU events description, which goes along with VTune help system.
If you experience other crashes of VTune, please submit the issue through the Premier Support system, it will guaranty that the problem will be recorded and considered.
What regards to the slowdown with VS 2008, its known problem. Check your system for the following environment variables:
If any are found, remove them and restart Visual Studio. It should eliminate the problem. If not, submit the issue to the Premier Support. For more information regarding this problem take a look at this support page.