Why would the library-activated serviced components put more load on db?

[Guest]

I wasn't sure what would be the best ng to post it.

We have ASP.NET app that uses serviced component to perform all database writes and updates (there are separate components sitting on the web server to do reads)

Initially, serviced components and ASP.NET app were on two separated machines and components had server activation

Since there is a substantial overhead in running serviced compoents as server (dllhost, interop, marchaling, etc), I decided to run the components as library and put them to the web server

We maybe gained some speed, but the database blocking increased substantially, and I am trying to understand why is that

Maybe because when the components run with server activation COM+ serializes the calls and thus the blocking is less

Thanks

-Sta

 

[Steven Cheng[MSFT]]

Hi Stan,


Thanks for posting in community. Based on my understanding, your serviced
component(COM+ , written in c++? or ..) used to be deployed as server
application and because of the speed considerance, you changed it to
library-activated. However, you found this turn the database service into
blocking , yes?

Have you tried providing a certain test application to test the
ServicedComponent both under Server-activated and Library-activated mode?
I'm not sure whether you've ever read the following tech article, it has
discussed on the performance comparsion on COM+ data access components:

#Performance Comparison: Transaction Control
http://msdn.microsoft.com/library/en-us/dnbda/html/bdadotnetarch13.asp?frame
=true

Also, I here are some other ones instruct us on creating own Performance
Monitor coutners for COM+ apps and debuging COM+ apps:
#Creating COM+ PerfMon Counters to Monitor COM+ Data
http://msdn.microsoft.com/library/en-us/dv_vstechart/html/concreatingcomperf
moncounters.asp?frame=true

#Debugging COM+ Applications
http://msdn.microsoft.com/library/en-us/cossdk/htm/pgdebuggingapplications_5
nn7.asp?frame=true

#Debugging COM+ 1.0 Components
http://msdn.microsoft.com/library/en-us/vsdebug/html/vxtskdebuggingcom10comp
onents.asp?frame=true

Maybe you may have a monitor focus on the components (out of the ASP.NET
app) to see whether we can find the root cause. Please have a check on the
above items. If you have any findings or further questions, please feel
free to post here.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Steven Cheng[MSFT]]

Hi Stan,

Have you had a chance to check out the item provided in my last reply or
have you got any progresses on this issue? If you have any updates or new
findings, please feel free to post here.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx