Under the Hood of .NET Memory Management - Simple Talk

More documents

Recommendations

Info

Chapter 5: Application-Specific Problems WPF also sets the lofty goal of minimizing the likelihood of data binding creating memory leaks. Among other things, WPF wants to make it simple and straightforward to bind data to the UI. control.ItemsSource = collection; Listing 5.25: Simple data binding. If the control in question is an ItemControl and the collection implements INotifyCollectionChanged, then the item control will automatically wire up to the collection's CollectionChanged event. This is both powerful and dangerous, as "easy" does not always also mean "sensible." For all that WPF takes a lot of complexity away from tired eyes, I hope you can see why it's worth being aware that that complexity still exists, and still needs to be factored into your code. Windows Communication Framework Windows Communication Framework (WCF) is Microsoft's solution for distributed computing and Service-Oriented Applications (SOA). With WCF you can spread the processing load over one or more servers, allowing you to put the presentation logic on one server and the data access / business logic on another. There are a couple of issues inherent in such a separation, but there are also some compelling reasons to follow this type of deployment model. 170
Chapter 5: Application-Specific Problems Benefits You may want to use this to better support connection pooling to the database, which is especially useful with desktop applications. You may want to do this to improve security, such that only the data servers need to be able to connect to the database, and the presentation servers can be blocked. This is especially useful with Internet-facing applications, where the presentation servers are in the Demilitarized Zone (DMZ), and everything else is safely behind the firewalls. You may want to do this to lower the cost of initializing an ORM system. Initializing an ORM such as Entity Framework or NHibernate can be expensive, and initializing all of the mapping/configuration information on the data server can lower the cost of starting up the presentation server. Instead of having to load the metadata for every page request, or even in the application start, you can load the metadata when the WCF host is started. Finally, you may want to do this to help solve bandwidth concerns; in some settings, you may find that the data passed back and forth between the database and the data server is more than the data passed back and forth between the data server and the presentation servers. With web applications, this may not be a major concern because they may well both be on the same network segment, and so the net effect is negligible. But with a desktop application, the database-to-data-server link may be a local network hop, while the data-server-to-presentation link may be a slow network hop over a lower bandwidth. Drawbacks The most obvious drawback is that method calls must now be marshaled across server boundaries. This may mean that something that looks like a simple method will actually be an expensive service method call. Essentially, we want to get all of the data we need in as few calls as possible, which also means we want to avoid a "chatty" interface. 171
Page 1 and 2:
.NET Handbooks Under the Hood of .N
Page 3 and 4:
Copyright November 2011 ISBN 978-1-
Page 5 and 6:
Workstation GC mode ...............
Page 7 and 8:
Section 3: Deeper .NET ............
Page 9 and 10:
I also want to thank the countless
Page 11 and 12:
Introduction Tackling .NET memory m
Page 13 and 14:
Section 1: Introduction to .NET Mem
Page 15 and 16:
Chapter 1: Prelude The truth is, by
Page 17 and 18:
Chapter 1: Prelude 7 { 8 int multip
Page 19 and 20:
Chapter 1: Prelude These are primit
Page 21 and 22:
Chapter 1: Prelude 1 void ValueTest
Page 23 and 24:
Chapter 1: Prelude On the other han
Page 25 and 26:
Chapter 1: Prelude Because paramete
Page 27 and 28:
Chapter 1: Prelude 1 int i=12; 2 Ar
Page 29 and 30:
Chapter 1: Prelude When an Order is
Page 31 and 32:
Chapter 1: Prelude Void Mark(object
Page 33 and 34:
Chapter 1: Prelude To access each m
Page 35 and 36:
Chapter 1: Prelude [ThreadStatic] p
Page 37 and 38:
Chapter 2: The Simple Heap Model Co
Page 39 and 40:
Chapter 2: The Simple Heap Model Wh
Page 41 and 42:
Chapter 2: The Simple Heap Model Fi
Page 43 and 44:
Chapter 2: The Simple Heap Model th
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Chapter 2: The Simple Heap Model Ob
Page 51 and 52:
Chapter 2: The Simple Heap Model ou
Page 53 and 54:
Chapter 2: The Simple Heap Model Pe
Page 55 and 56:
Chapter 2: The Simple Heap Model La
Page 57 and 58:
Chapter 2: The Simple Heap Model Ul
Page 59 and 60:
Chapter 3: A Little More Detail Now
Page 61 and 62:
Chapter 3: A Little More Detail It'
Page 63 and 64:
Chapter 3: A Little More Detail In
Page 65 and 66:
Chapter 3: A Little More Detail Con
Page 67 and 68:
Chapter 3: A Little More Detail Bac
Page 69 and 70:
Chapter 3: A Little More Detail Alt
Page 71 and 72:
Page 73 and 74:
Chapter 3: A Little More Detail Wea
Page 75 and 76:
Chapter 3: A Little More Detail …
Page 77 and 78:
Chapter 3: A Little More Detail GC
Page 79 and 80:
Page 81 and 82:
What's Coming Next In this next sec
Page 83 and 84:
• Use a struct to represent any i
Page 86 and 87:
Chapter 4: Common Memory Problems T
Page 88 and 89:
Chapter 4: Common Memory Problems V
Page 90 and 91:
Chapter 4: Common Memory Problems c
Page 92 and 93:
Chapter 4: Common Memory Problems i
Page 94 and 95:
Chapter 4: Common Memory Problems u
Page 96 and 97:
Page 98 and 99:
Chapter 4: Common Memory Problems i
Page 100 and 101:
Chapter 4: Common Memory Problems S
Page 102 and 103:
Chapter 4: Common Memory Problems p
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Chapter 4: Common Memory Problems s
Page 110 and 111:
Chapter 4: Common Memory Problems Y
Page 112 and 113:
Chapter 4: Common Memory Problems v
Page 114 and 115:
Chapter 4: Common Memory Problems {
Page 116 and 117:
Page 118 and 119:
Page 120 and 121: Chapter 4: Common Memory Problems [
Page 122 and 123: Chapter 4: Common Memory Problems p
Page 124 and 125: Chapter 4: Common Memory Problems D
Page 126 and 127: Chapter 4: Common Memory Problems T
Page 128 and 129: Chapter 4: Common Memory Problems C
Page 130 and 131: Chapter 4: Common Memory Problems W
Page 134 and 135: Chapter 4: Common Memory Problems [
Page 136 and 137: Chapter 4: Common Memory Problems A
Page 140 and 141: Chapter 4: Common Memory Problems U
Page 142 and 143: Chapter 4: Common Memory Problems T
Page 144 and 145: Chapter 4: Common Memory Problems K
Page 146 and 147: Chapter 5: Application-Specific Pro
Page 178 and 179: Section 3: Deeper .NET
Page 180 and 181: Chapter 6: A Few More Advanced Topi
Page 198 and 199: Chapter 7: The Windows Memory Model
Page 214 and 215: .NET and SQL Server Tools from Red
Page 216 and 217: .NET Reflector ® Decompile, browse
Page 218 and 219: SQL Prompt Pro Write, edit, and exp
Page 220 and 221:
SQL Monitor SQL Server performance
Page 222 and 223:
SQL Toolbelt The essential SQL Serv
Page 224:
Brad's Sure Guide to SQL Server Mai
show all

Under the Hood of .NET Memory Management - Simple Talk

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?