> I generate a dump file, I realize that I will not be able to
pinpoint
> what exactly causes this behavior. I'm wondering if there is a
general
> site or any pointers you guys can give to help me out when trying to
> program with performance in mind?

> On a few appliactions that I've witnessed for sample and conceptual
> analysis, I've seen the overuse of datasets, when datatables could
be
> used. Is creating a dataset object overkill on memory, or is the
> difference negligble? Also, I've seen the explicit closing and

> someone that this is indeed not the right way to go about things. I
was
> told that the Fill method of a DataAdapter will open and close the
> connection as needed. Is this correct? And what consequences would
I
> face if I opened and closed the connection manually?

Michael Giagnocavo [MVP] wrote:
>>I generate a dump file, I realize that I will not be able to
>
> pinpoint
>
>>what exactly causes this behavior. I'm wondering if there is a
>
> general
>
>>site or any pointers you guys can give to help me out when trying to
>>program with performance in mind?
>
>
> msdn.microsoft.com --- there are a few great articles on performance
> with the CLR and how to get the most out of it, as well as
> understanding how the GC works (important).
>
> The BEST thing to do is test. Run tests on everything, as that's the
> best way to find out what the REAL cost is. For high-precision, use
> Kernel32.dll!QueryPerformanceCounter.
>
> Also, the Performance Counters that .NET installs for use with the
> Performance Monitor are great (see how many GCs have passed, how much
> RAM/CPU used, etc.). As well, you might want to install a CLR
> Profiler (there's one available at MSDN) to look into memory issues.
>
>
>>On a few appliactions that I've witnessed for sample and conceptual
>>analysis, I've seen the overuse of datasets, when datatables could
>
> be
>
>>used. Is creating a dataset object overkill on memory, or is the
>>difference negligble? Also, I've seen the explicit closing and
>
> opening
>
> It will take some extra memory, but it's not overkill. If you have
> 500k of data, a few more bytes for the DataSet isn't going to make a
> huge difference. An object costs 12 bytes + the bytes for its fields.
> Looking at the DataSet class, I don't think it's a lot of memory.
> However if you have a small amount of data, like only one row with a
> few fields, then you might want to consider alternative ways of
> sending the data, if it is a performance critical section.
>
>
>>someone that this is indeed not the right way to go about things. I
>
> was
>
>>told that the Fill method of a DataAdapter will open and close the
>>connection as needed. Is this correct? And what consequences would
>
> I
>
>>face if I opened and closed the connection manually?
>
>
> I believe if you open and close it manually, it should have a minimal
> effect (it should only need to check the connectionstate). If you are
> going to use it a few times in a row, you might want to leave it open.
> Again, performance testing could show any real difference.
>
> -mike
> MVP
>
>