Jump to content
Forumu Destekleyenlere Katılın ×
Paticik Forumları
2000 lerden beri faal olan, çok şukela bir paylaşım platformuyuz. Hoşgeldiniz.

VB SendKey


SimasheR

Öne çıkan mesajlar

said:
Henuz okumamis iseniz, siddetle Jeffrey Richter/Microsoft Press - Applied Microsoft .NET Programming kitabina goz gezdirebilirsiniz. Orada yeterince CPU/OS tabanli optimizasyondan bahsediliyor.

Sayfa rica edeyim. çünkü kitapda sizin söylediğiniz gibi multi process iyileştirmesini ben göremedim. Hatta çoklu cpu 'a sahip sistemlerden bahsedilmiyor bile (sadece garbage col'da bir satır var..)
Link to comment
Sosyal ağlarda paylaş

kitabi en sonunda alabildim,
Applied Microsoft .NET framework programming Jeffrey Richter/ MS Press
sayfa 18

Believe me, since I approached the CLR from a c/c++ background myself, I was quite skeptical and concerned about this additional overhead. The truth is that this second compilation stage that occurs at run time does not hurt performance and it does allocate dynamic memory. However Microsoft has done a lot of performance work to keep his additional overhead to a minimum.

...

In fact, you'll probably find this hard to believe, but many people(Including me) think that managed applications could actually outperform unmanaged applications. There are many reasons to believe this, for example when the JIT compiler compiles the IL code into native code at run time, the compiler knows more about the execution enviroment than an unmaganed compiler would know. Here are some ways that managed code could outperform unmanaged code :


-- A JIT compiler could detect that the application is running on a Pentium 4 and produce native code that takes advantage of any special instructions offered by the Pentium 4, usually unmanaged applications are compiled for the lowest common denominator CPU and avoid using special instructions that would give the application a performance boost over newer CPUs.
-- A JIT compiler could detect that a certain test is always false on the machine that it is running on. For example, consider a method with a code like this:

If(NumberofCpus > 1){
..
}
This code could cause the JIT compiler not to generate any CPU instructions if the host mahcine has only one CPU. In this case, the native code has been fine-tuned for the host machine : the code is smaller and executes faster.
--The CLR could profile the code's execution and recompile the IL into native code while the application runs. The recompiled code could be reorganised to reduce incorrect branch predictions depending on the observed execution patterns.
Link to comment
Sosyal ağlarda paylaş

Gördüğün gibi birden falza cpu'lu sistemler için optimize eder DEMİYOR !
Hatta bakalım, ne diyor ??? Eğer Cpu'yu sayısına göre bir optimizazyonun farkına varırsa (ki mechül !) birden fazla cpu'su olmayan sistemde, çoklu cpu kodunu msil'den native geçirmez diyor.... Boşuna iş yapmaz...

"This code could cause the JIT compiler not to generate any CPU instructions if the host mahcine has only one CPU."


Sizi okuma yazma kurslarına alalım...

"A JIT compiler could detect that the application is running on a Pentium 4 and produce native code that takes advantage of any special instructions offered by the Pentium 4,"

Pentium 120'den bu yana tüm cpu'lara ele alalım ve yapılacak "hangi yeni iyileştirme" ver bi göz atalım.. MMX,SSE,SSE2....
herhangi birini kullanmak zaten için saf asm'ye ihtiyaç var... Onun dışındada pek yeni opcode yok zaten :),

Demiş orada yok P4 için daha hızlı bir kod üretir vb.... Hangi yeni opcode varki p4'de (bunların dışında !)
güldürmeyin beni..
Link to comment
Sosyal ağlarda paylaş

×
×
  • Yeni Oluştur...