People often get angry when people try and hijack threads - (it makes the archives very hard to read too).
I'm sure if someone has a answer to your question, they will answer it in the other thread you created already. On 14 April 2010 18:57, Brent Lewis <coder0...@hotmail.com> wrote: > > How do I make the mouse cursor visible? I'd rather not resort to calling > the Win32 API directly. Please help. > > > Date: Wed, 14 Apr 2010 19:19:57 +0200 > > From: marek.sierad...@gmail.com > > To: hlcoders@list.valvesoftware.com > > Subject: Re: [hlcoders] Source Profiling > > > > There are 2 ways of doing profiling: > > - instrumentation (VProf) > > - sampling > > > > VProf covers only some stuff. If you want to get accurate data and for > > parts that are deep in the engine you should use sampling. AMD > > CodeAnalyst or Intel VTune. If you use Linux for profiling, you will > > have access to symbols for engine library files. When I did the > > profiling it was really helpful because most of CPU load was in the > > networking in the engine because I sent too much. What's really cool > > in VTune/CodeAnalyst is checking how much on average each instruction > > in C++/asm took. (it's an average due to out-of-order execution) > > > > You should expect that most of CPU time is spent in the engine and you > > should try to find which part of the mod causes most of it. > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
