Re: .NET slows, COM+ still fast
- From: "Mike Jansen" <mjansen_nntp@xxxxxxxx>
- Date: Mon, 7 Nov 2005 11:07:14 -0500
Thanks for the info.
Do you happen to know if you can scale up or out to help with Web service
performance? It's not ideal, but I think our bigger customers that require
the 300+ concurrent connections would be willing to add hardware if it made
the system work.
I'd hate to write stuff from scratch in something that's not going to be
supported in the near future but I don't want to choose the newer stuff that
doesn't perform.... I'm sure there are many out there familiar with that
pain.
Thanks again,
Mike
"BigBB88" <BigBB88@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8FE69359-1EE6-4485-9136-1787964A0ED4@xxxxxxxxxxxxxxxx
> Mike,
>
> We are getting the same story from Microsoft. Use Web Services! When we
> say Web Services will handle the load but at a cost of performance, they
> say
> "Well Indigo will fix this". Yea and we are going to wait two years for
> Indigo! Our app is working, but we have other issues now, we are getting
> winsock errors, we think its Network, but the network folks are saying its
> how .NET Remoting interacts with the network that is causing the problems.
> Essentially the user PC's are locking our .NET client out with winsock
> errors, which essentially locks our app and users have to ctrl-alt-del and
> end task to get out, since .NET also doesn't have any easy way to time
> users
> out!
>
> "Mike Jansen" wrote:
>
>> Have you gotten any new information on this? I'm currently investigating
>> middle-tier .NET options for 300-1000 concurrent users and someone
>> pointed
>> me to this thread. From what I am seeing, remoting isn't Microsoft's
>> future. They actually recommend web services which according to their
>> own
>> kb articles, performs worse than remoting.
>>
>> We have a need for a high-performing middle-tier and would like to stick
>> with the direction Microsoft is promoting but we need to be sure it can
>> handle what we need to do. If you've learned anything new since this
>> post,
>> I'd gladly hear about it. Did you ever get a response from Microsoft?
>>
>> Mike
>>
>>
>> "BigBB88" <BigBB88@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:FB326038-A05C-4445-B9C2-72F64CB235FA@xxxxxxxxxxxxxxxx
>> > We have two applications that perform the same functions and run on the
>> > same
>> > server. This is a traditional 3-tier app using VB client - Proxy-
>> > MidTier
>> > (in c++) and SQLServer/Messaging connectivity in a COM+ (DCOM)
>> > environment.
>> > The application was re-developed recently using VB.NET - Remoting - C#
>> > on
>> > the
>> > MidTier to the Messaging/SQLServer connectivity layer. Both
>> > applications
>> > are
>> > running under a Windows 2000 Clustered (Active/Passive) enterprise
>> > Compaq/HP
>> > server with 8GB RAM (PAE Enabled) and 8 CPU's. There are 300 total
>> > users
>> > using the .NET application and 800+ users using the VB client for a
>> > total
>> > of
>> > over 1100 users. We are trying to port all users over to .NET, but the
>> > performance is so bad (under 300 users) we currently cannot do so. On
>> > the
>> > same box at the same time, the .NET application (identical in
>> > functionality
>> > to the COM+ application) chokes (VERY SLOW, almost unuseable), while
>> > the
>> > COM+
>> > application seems to be fine. We have looked at Memory, CPU and
>> > Networking
>> > utilization and all look to be within acceptable levels. Another .NET
>> > application ustilizing the same .NET service (different functionality)
>> > is
>> > also extremely slow. We have captured a dump using the Microsoft
>> > Debugging
>> > tools during this slow period and sent it off to MS. Is there anything
>> > else
>> > we can do or look at they may be causing .NET to be so much slower then
>> > the
>> > identical (in functionality) application using the COM+ model?
>>
>>
>>
.
- References:
- Re: .NET slows, COM+ still fast
- From: Mike Jansen
- Re: .NET slows, COM+ still fast
- Prev by Date: Re: 1.1 perf versus 2.0
- Next by Date: Re: Datagrid cell position and textboxes
- Previous by thread: Re: .NET slows, COM+ still fast
- Next by thread: Re: .NET slows, COM+ still fast
- Index(es):
Relevant Pages
|
Loading