Mon, Apr 23 2007 18:35
bradley
People who understand .Net apply here
People these days always say thing like .. "oh does it have the source code?" or "oh is it open source?"
Well...here's the thing folks... the ability to look at the underlying code only helps you if you know what the heck you are looking at. For most small business owners, heck for most small business integraters, looking at the "source" code is like me reading KB821268, looking under the hood of the blog server and trying to figure out exactly where in the .NET 2.0 machine.config file that I'm supposed to enter some words and values to try to get Yoda to stop sucking CPU cycles. Well.. at least I hope that is the trick because right now I know that I haven't a clue about what I'm doing.
Oh yeah, I can do a search of the Community server site and find stuff... like posts on forums and what not...and yup I've followed that one and it's not helping...
Application Pool setup screenshots - Community Server:
http://communityserver.org/forums/p/482755/560894.aspx
But when you aren't a coder, and you haven't a clue what you are doing, all this is is "data" not "valuable information" when you don't have a clue of what you are doing and the KB articles assume a basic level of knowledge that isn't in my noggin'.
To me, this what the business decision maker in me makes the cut between stuff for the firm (the business) and stuff for ... well the blog.
S*U*P*P*O*R*T
The level and quality of support of a product are what make me stay with a product, leave a product, look forward to the next product. And while, I'm sure all of us will agree support with Microsoft products can be dicey sometimes, if you get to a support person who knows their stuff, you relax knowing that your server is in good hands. If you don't have that trust of the person "driving" your server, you are in for a bumpy ride. Right now this server has a bumpy ride because it's primary support person (aka ME) hasn't a bloody clue (as Nick would say) and so far I don't think I'm helping and only hurting with my taking the bits and pieces along the way.
Because I'm not trained in this, and getting bits and pieces of stuff along the way, I'm not getting the right answer, I'm just getting data that I think might be the answer. We see this in network configurations, don't we? Someone who gets a bit of information from over there... and a tad from this blog over there...and you end up with network ....or in my case.... a blog server that isn't too healthy and well thought out.
<sigh>
Pardon me while I go find a real expert in this stuff because I really don't have a clue....

Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications:
http://support.microsoft.com/kb/821268/en-us
<processModel maxWorkerThreads="100" maxIoThreads="100" minWorkerThreads="50">
<httpruntime minFreeThreads="176" minLocalRequestFreeThreads="152">
<connectionManagement>
<add address="IPofserver" maxconnection="48"/>
</connectionManagement>
Filed under: News