On 28/10/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
> Steve Jones wrote:
> > Note here I'm talking about the 95%+ of applications which measure
> > end-to-end performance in the second or 1/10 second margins, not at
> > the micro-second level.
>
> If people interactions are involved, you need to think about how those 1/10
> second margins add up. It might not be appreciable, but the network
> bandwidth
> used and the latency involved on certain networks can make particular
> applications unrealizable. With the mobile information network growing, and
> the
> charges by the KB for data, this can be an issue too.
I mean 1/10 second end to end times, I agree that a 1/10 second soon
starts adding up, but most of the elements I've seen are still done in
the sub millisecond element and in comparison with parsing and
generating HTML (or compiling a JSP page) the XML parsers seem much
more performant.
In a mobile environment I've not seen it that much of an issue, even
back in pre-GRPS days you could do WS on a mobile device, the key as
you say is the envelope size (don't use standard based schemas like
OTA) not so much the actual marshalling/unmarshalling (which is the
CPU bound element).
>
> > So while XML might be one of the most inefficient transports ever
> > dreamed of. Is it really an area where most organisations should
> > worry about performance given the current hardware characteristics?
>
> It should be a measured consideration I think. You have to decide how much
> you
> can spend on "measuring" to decide what the "costs" are.
I agree, it should be zero, but in a decently architected system has
anyone had any experience at what level it becomes an issue? Most
times I've seen WS performance issues its traditional problems, too
fine grained a set of calls, using DOM on massive XML documents where
you should only care about the header information etc etc.
>
> > What is the experience out there? Is XML performance really that bad
> > in most software stacks that dedicated solutions are required? Stats
> > and data most appreciated.
>
> If you need mobile code, then XML gets in the way because you don't really
> gain
> anything by "wrapping" code in XML. Mobile code in the server environment
> really increases the rate and simplification of distribution of updates. You
> can install updates in one place, and everyone gets the update.
I'd agree that mobile code isn't a great idea in WS-* (or REST) land,
and it unfortunately looks like people are developing new standards to
be exactly that.
>
> Gregg Wonderly
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
