single large vs multiple small SP calls - speed + efficiency

[John B]

I have a collection of objects (eg Forms) , each of which contains another
collection (eg Controls). When I come to fill the Control collections at
startup, I fill each one in turn using a Form.GetControls(FormID) call. This
puts the call where I think it is best placed (In the Form class), but am
unsure about the efficiency of it. Would I be better off making one "global"
call, retuning all the Controls and then filling each of the Form.Controls
collections.

I know I could probably test it somehow, but does anyone know what the best
way to do it would be?

Ideas welcome.

Thanks

 

[Keenan Newton]

Well unfortunatlry I think it realy comes down to the desing and
ultimate goals of your application. If you are building just a simple
clinet/server application. That will probably never grow beyond 5 to
10 users then this is fine. However, if this is a larger application
where you have 50 plus users using it. You want to insure scalablity
by breaking it out into multiple physical tiers, then I suggest getting
everything at once. Since with a n-tier application a typical bottle
next is application domain to application domain calls.