.NET Compiler Optimization

Question

I am writing an application that I need to run at an incredibly low processor speed. The application creates and destroys memory in a creative style throughout its launch, and it works fine. What compiler optimizations are happening, so I can try to do this?

One trick is that the CLR processes arrays much faster than lists, so if you need to process tons of items in a list, you might be better off not calling ToArray () and processing it, rather than calling ElementAt () again and again.

Answer 1

, , , , . Stack Overflow, Google , .

- , , .

Answer 2

, , .

. - . .

, ... , , , , . CLR/ .

StringBuilder - : . , , - , . , .

Answer 3

, StringBuilder . .

(+ ) StringBuilder.

Windows Forms.NET DataGridView.AutoSizeColumnsMode AutoSizeRowMode.

Answer 4

, - ; :

• - ? ? .. ( ) ?
• - ? ( , DynamicMethod ..) - , Reflection.Emit?
• unsafe? ( , , ).
• ( , ) - IL? ( - ), , , . (, , - IL), () stloc/ldloc ( )

, , . , , , , .

Answer 5

, , List. CLR , . , , unsafe, . , , .

Answer 6

( ), , . , - , , , , .

, , , - , .

. " ", . , , , .

Answer 7

(GC) GC.Collect. GC, , , GC.Collect .

For a specific GDI +, call Invalidateto nullify the client area or a specific rectangle of the control or form instead of calling Refreshthat call Invalidateand updateto redraw the control.