Re: LOH behavior

Tech-Archive recommends: Speed Up your PC by fixing your registry

Ignacio Machin ( .NET/ C# MVP ) wrote:
Hi,,

"Frank Rizzo" <none@xxxxxxxx> wrote in message news:euOvqQPNHHA.4376@xxxxxxxxxxxxxxxxxxxxxxx
| Ignacio Machin ( .NET/ C# MVP ) wrote:
| > Hi,
| >
| > "Frank Rizzo" <none@xxxxxxxx> wrote in message
| > news:OnrGscONHHA.1276@xxxxxxxxxxxxxxxxxxxxxxx
| >> With this in mind, if I load a DataSet that that contains 100MB of data,
| >> what exactly (if anything) goes to LOH?
| >
| > First of all, with this amount of data you will have A LOT more to worry
| > about that the memory, parsing it will be a killer!!!
|
| Actually, it takes about 20 seconds to bring the data into the client
| and 4 seconds to build an object tree. And this is on my 2 year old
| laptop. The app will be on a powerful server.

4 s for a 100MB dataset?

I have problems when the dataset goes over 10MB , it takes like 30 s to load it.

They the price of creating/adding a new object is too high. Make sure that the constructor does nothing but simply populate properties.
My dataset is divided into several tables which all bring related information. Do not use the related tables feature because it simply slows the living hell out of the process. Besides, it is kind of useless, since all the data in the dataset must be loaded into the object tree. So I simply loop through each table and use hashtables (created on the fly) to keep track of related information in DataTable objects.





.