"John A Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:eVCzOeXbGHA.4672@TK2MSFTNGP04.phx.gbl...
> I'm trying to determine the relative performance of three implementations
> of data-access classes in ASP.NET 2.0 :
>
> 1. non-singleton classes with non-static methods which must
> instantiate a class object (possibly multiple times) in each method
> involved in processing a page request
>

"John A Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:eVCzOeXbGHA.4672@TK2MSFTNGP04.phx.gbl...
> I'm trying to determine the relative performance of three implementations
> of data-access classes in ASP.NET 2.0 :
>
> 1. non-singleton classes with non-static methods which must
> instantiate a class object (possibly multiple times) in each method
> involved in processing a page request
>
> 2. singleton classes that implement a getInstance() method that
> provides a pre-existing instance of the class if one exists; if an
> instance does not exist, getInstance() instantiates a class object and
> assigns it to an internal static reference
>
> 3. classes where all data-provision methods in the interface are
> implemented as static methods
>
>
> In the course of writing a scalable ASP.NET 2.0 web-app, has anyone done
> any benchmarking (either formal or informal) ... or has a general sense
> of the relative peformance of these 3 implementations ?
>
> Does anyone know of any whitepapers or other studies that might be
> available ( either MS or external ) ?
>
>
>
>
>
>
>
>