P
Peter Bär
A Question to the C#/.Net Gods of this forum:
are there performance penalties when i compile (C#, FW1.1, ASP.NET,
Studio2003) a central baseclass in a different assembly than all the
derived classes?
f.i. ive got a class dbobject i project "Basesupport", compiles to
Basesupport.dll.
From dbobject i derive about 100 classes, thy all are located in Project
XYBiz, so they are compiled to XYBiz.dll.
doughter classes make heavy use of properties, methods and attributes from
the mother class (about 100 per method call)
Now, i dont know whether that design wouldnt produce a performance penalty
for jumping between user dlls, switching contexts, dlls, whatever.
Approximation one aspx page (resulting in 1 database call(storeproc-
SQLserver)) uses 5 objects, 3 methodcalls each, with - as i said, about 100
cross-assembly-calls. Summed up, thats about 1500 cross-assembly-calls.
Ok, i know, i know, "code is fast and db is slow, and therefor dont think
about performance, cause db is bottleneck anyways".
But i just wann aknow in principle whether there is no, just a tiny or
noticeable performance penalty from Framework & IIS, when they have to
ping-pong between two user-dlls 1500 times per page call...
Many thanks in advance &
cheers from Vienna
are there performance penalties when i compile (C#, FW1.1, ASP.NET,
Studio2003) a central baseclass in a different assembly than all the
derived classes?
f.i. ive got a class dbobject i project "Basesupport", compiles to
Basesupport.dll.
From dbobject i derive about 100 classes, thy all are located in Project
XYBiz, so they are compiled to XYBiz.dll.
doughter classes make heavy use of properties, methods and attributes from
the mother class (about 100 per method call)
Now, i dont know whether that design wouldnt produce a performance penalty
for jumping between user dlls, switching contexts, dlls, whatever.
Approximation one aspx page (resulting in 1 database call(storeproc-
SQLserver)) uses 5 objects, 3 methodcalls each, with - as i said, about 100
cross-assembly-calls. Summed up, thats about 1500 cross-assembly-calls.
Ok, i know, i know, "code is fast and db is slow, and therefor dont think
about performance, cause db is bottleneck anyways".
But i just wann aknow in principle whether there is no, just a tiny or
noticeable performance penalty from Framework & IIS, when they have to
ping-pong between two user-dlls 1500 times per page call...
Many thanks in advance &
cheers from Vienna