Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Mac OS X Java Performance

> -----Original Message-----
> From: Greg Guerin [SMTP:email@hidden]
> Sent: Thursday, July 31, 2003 11:43 AM
> To: email@hidden
> Subject: Re: Mac OS X Java Performance
>
> "Hall, Michael J." <email@hidden> wrote:
>
> >What if + is implemented differently on different architectures?
>
Greg Guerin

> Hence the qualifiers "almost" and "reasonable". Anywhere it can't be done
> in one instruction is unreasonable.

> I wasn't questioning the use of some slightly vague terms in the statement. We probably should all tend to be more tolerant of vagueness and wary of absolutes and generalities.
I was somewhat questioning the oversimplification of the a+b = c example. I think any number of languages can deliver the case of a+b = c on many architectures.
What I was also trying to point out was that on the day this example was mentioned we had a more involved 'real' world example where the same behavior for the same code in Java didn't appear to hold up, java.io.DataOutputStream writing performance, across two specific not minor architectures.
I am aware that there are tests that Java code must pass to qualify as Java releases. I am assuming both the Windows implementations here at work and the Mac JVM releases have passed these tests.
I am aware that there is a language specification that defines what the behaviors of Java classes should be. I haven't looked at it for either the case of a+b = c or DataOutputStream but I am assuming again that neither of the Windows and Mac implementations vary drastically from this specification.
So, is this acceptable and Windows should just be commended in this case for overachieving and providing a DataOutputStream that performs better than it needs to? Should the Mac JVM be questioned because it provides an under-achieving one? Should we just say its a platform quirk and try to remember to always buffer? Should the JVM qualifications include performance requirements as part of the behavior spec? What then when the Mac meets it and Windows overachieves it? Some developer moving over from Windows to Mac is still going to be just as badly off when all of a sudden his code slows down.
Again, doesn't a+b = c just sort of oversimplify?

Mike Hall <email@hidden>
<http://www.spacestar.net/users/mikehall>
_______________________________________________
java-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/java-dev
Be sure to read the FAQ http://developer.apple.com/java/faq/ before posting
Do not post admin requests to the list. They will be ignored.


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.