In terms of performance which of the following is better:
A large dll containing many Vb components
Or many dlls containing one or two Vb components.
Note: The dll's would run in COM+
Printable View
In terms of performance which of the following is better:
A large dll containing many Vb components
Or many dlls containing one or two Vb components.
Note: The dll's would run in COM+
They always told me size didn't matter. It's all about personality.
large dll containing many Vb components has more personality, but would probably have the responses of a snail
many dlls containing one or two Vb components has no personality, but would probably have the responses of a jet fighter.
Oh yes.
The overhead for a DLL is relatively fixed in size. So if you had one DLL that was 10X in size, then it would have an overhead of 1Y. Where as if you had 10 DLLs that were 1X in size then would have an overhead approaching 10Y.
But... if you don't need to call them all at once, and if you want to add 'mobility' to your app (you can switch out single smaller DLLs and not have to recompile one big one), then ten smaller ones is the way to go. You won't notice the 10Y because you may only invoke 1X and 1Y at a time, instead of being forced to invoke 10X and 1Y.
Now I have a question... is it faster to make 1 SQL query for 10 days of data, or 10 queries for 1 day each?
I would have to imagine that it is faster to make one query.