How to avoid "binding to large CLR objects"?

Question

This DataBinding Optimization Guide says:

A significant performance impact affects data binding to a single CLR with thousands of properties. You can minimize this effect by splitting one object into several CLR objects with fewer properties.

• What does it mean? I'm still trying to get familiar with DataBinding, but my analogy here is that the properties are similar to the fields of an SQL table, and the objects are rows. This tip then translates as "to avoid problems with more fields, use fewer fields, and create more rows." Since this makes no sense to me, is it possible that my understanding of data binding is completely distorted?

• Does this advice really apply? I'm not sure if it is specific to .NET 4 / WPF, while I am using 3.5 and a WinForms-based user management library (DevExpress)

• Aside: Do I think that DataBinding uses reflection when using a data source like IList?

This is not just an academic question. I'm currently trying to speed up loading of XtraGridView (DevExpress Control) with ~ 100,000 objects with 50 properties or so.

Answer 1

This tip then translates as “to avoid problems with more fields, use fewer fields and create more rows”

, " " (.. ). "[...] ", . , "" ​​...

, , , , ... , OO.

? , .NET 4/WPF, 3.5 WinForms (DevExpress)

, , , WPF, , WinForms ( , )

: , DataBinding IList?

... TypeDescriptor, CLR. , : ICustomTypeDescriptor, , .. (DataTable - )

Answer 2

. , , , 5 . . .

. , , , , , , . dbase . .