OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: ArunKumar (akumarOMNESYSINDIA.COM)
Date: Wed Feb 27 2002 - 23:00:54 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Well i did have a chance to look at a somewhat similar
    situattion and we could finally reduce it and iron out the
    mess -

    The problem was IIS was running as out of process +
    the whole COM+ solution was running as 3 different
    COM+ packages - Database was also in the same
    machine

    Now this is a pretty loaded machine and with this prutty
    bad ASP coding was being used , which would call
    components in loop repeatedly to access server side
    recordsets (adding fuel to fire) - these component were
    also calling component across other packages and et
    all -

    I would ask you to make all comps part of single package
    and ASP also an out of process MTS package + look
    at the construction of ASP pages - typically you would
    want to reduce the no of comp calls to a minimum a single
    call if possible (3-5 is ok) -

    AAAAAnd be wary of com calls made in loops - thats
    the perfect candidate for context switch shooting off the
    roof - if possible return fully constructed page data in the
     form of variant arrays etc, instead of returning multiple
    recordsets(client side only) and then looping about them

    hope it helps
    arun

    ps : and hey if possible give that machine a break and
    move out something from it - it might be that this is just
    that ur machine is too loaded for the amount of access it
    handles - good luck

    ----- Original Message -----
    From: "Robert Sedor" <rsedorHOTMAIL.COM>
    To: <DCOMDISCUSS.MICROSOFT.COM>
    Sent: Wednesday, February 27, 2002 8:28 PM
    Subject: COM+ OLE-DB performance

    > We have a couple of testers here who have never tested anything on Win2k
    > before, and they are freaking out because when they stress our components,
    > which use OLE-DB and session pooling in COM+, the context switching and
    CPU
    > usage on the server goes way up. Their claim is that on Winnt and MTS,
    the
    > higher the number of windows context switches and the higher the cpu
    usage,
    > the worse the overall performance.
    >
    > Can anyone point me to some type of documentation explaining this. I
    think
    > they are full of stuffing! They are running the components on the same
    > machine as IIS/ASP and access the database on another machine.
    >
    > Thanks
    >
    > ----------------------------------------------------------------
    > Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    > contains important info. Save time, search the archives at
    > http://discuss.microsoft.com/archives/index.html .
    > To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM
    >

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM