Re: XML/A Performance

From: Akshai Mirchandani [MS] (akshaim_at_online.microsoft.com)
Date: 02/11/04 

Date: Wed, 11 Feb 2004 14:30:11 -0800

Were you using Integrated Authentication or was it Anonymous? My belief is
that this perf issue is being caused by the fact that we didn't properly
support Keep-Alives of HTTP 1.1 and so for authenticated connections the TCP
connection was being destroyed and re-created for every request. This would
also cause authentication to be done for every message instead of only once
for the first connection.

Thanks,
Akshai 

--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Zoltan Grose" <zgrose@mac.com> wrote in message
news:2004021013352416807%zgrose@maccom...
> In my Java <-> XMLA application I see execution times < 300 ms so I'm not
> sure that is the case. In my case it was an Execute call returning maybe
50
> or 60 rows of data.
> -z
>
>
> On 2004-02-06 14:09:59 -0800, "Mosha Pasumansky [MS]"
> <moshap@online.microsoft.com> said:
>
> > I suspect the culprit is Nagle algorithm in ISAPI which adds 300ms
> latency
> > to every roundtrip. I don't know whether it is possible to disable it -
> > maybe you can direct this question to IIS and/or ISAPI newsgroups.
> >
> > -- 
> > ==================================================
> > Mosha Pasumansky  - http://www.mosha.com/msolap
> > Development Lead in the Analysis Server team
> > All you need is love (John Lennon)
> > Disclaimer : This posting is provided "AS IS" with no warranties, and
> > confers no rights.
> > ==================================================
> > "Wayne M" <wmdev@yahoo.co.uk> wrote in message
> > news:176adae9.0402050755.5be7b181@posting.google.com...
> > > Hi
> > >
> > > We are having great performance issues with XML/A. I have been trying
> > > to isolate the problem by doing some timings.
> > >
> > > The environment for these tests is VS.NET 2003/.NET 1.1. Analysis
> > > Services resides on the local machine. We're using Integrated
> > > Authentication and Dimensional Security.
> > >
> > > Example 1:
> > > Execute 40 discovers, 20 MDTREEOP_SELF and 20 MDTREEOP_PARENT, each on
> > > different members of a dimension. Connections are being reused so the
> > > data should be cached. However each operation is consistently taking
> > > approximately 0.37 seconds. This does not seem reasonable given the
> > > caching.
> > >
> > > Example 2:
> > > Run 20 Executes of the same MDX Query. Again, data should be cached as
> > > the connection is being reused. Queries subsequent to the first are
> > > consistently taking 0.48 seconds. If I run the same query in MDX
> > > Sample App (which uses ADOMD) the response is immediate - I've not
> > > been able to time, but it's easy to see it's not half a second.
> > >
> > > I've isolated these examples, however our real problem is that our
> > > load balanced solution is performing extremely badly under load.
> > >
> > > Has anybody had any experience of similar XMA/A performance problems?
> > >
> > > Any help appreciated.
> > > Wayne
> >
> >
> >
>
>

Relevant Pages

  • understanding chkrootkit: sshd section
    ... Rhosts Authentication disabled, originating port will not be trusted. ... Secure connection to %.100s on port %hu refused%.100s. ... Warning: Remote host refused compression. ... Received RSA challenge from server. ...
    (comp.os.linux.security)
  • understanding chkrootkit: sshd section
    ... Rhosts Authentication disabled, originating port will not be trusted. ... Secure connection to %.100s on port %hu refused%.100s. ... Warning: Remote host refused compression. ... Received RSA challenge from server. ...
    (comp.security.unix)
  • (fwd) FreeBSD Security Advisory FreeBSD-SA-01:39.tcp-isn (fwd)
    ... susceptible to attack than other unencrypted sessions. ... > incoming connection is being established, ... > All versions of FreeBSD 3.x and 4.x prior to the correction date ... > requiring other authentication of the originator are vulnerable to ...
    (FreeBSD-Security)
  • Re: understanding chkrootkit: sshd section
    ... Connection will not be encrypted. ... > Rhosts Authentication disabled, originating port will not be trusted. ... > Could not request local forwarding. ... Remote host failed or refused to allocate a pseudo tty. ...
    (comp.security.unix)
  • Re: understanding chkrootkit: sshd section
    ... Connection will not be encrypted. ... > Rhosts Authentication disabled, originating port will not be trusted. ... > Could not request local forwarding. ... Remote host failed or refused to allocate a pseudo tty. ...
    (comp.os.linux.security)
Loading