@Hador:
Tanto per curiosita', mi son permesso di effettuare qualche bench sulla jvm (aggiornata alla release di questa news) di Mac Os X...
Come base di riferimento per il test ho preso questa rece:
http://www.phoronix.com/scan.php?page=article&item=java_vm_performance&num=1
Che fa utilizzo del bench Phoronix...
Per questioni di tempo ho eseguito solo il bench java-scimark2; i risultati che ho ottenuto su di un macbook pro 13.3" con
[email protected], 4GB RAM, 160GD HD @5400rpm, sono i seguenti (in MFLOPS):
FFT: 442.22
SOR: 886.05
Montecarlo: 264.95
Composite: 725.35
Come puoi osservare il confronto e' nettamente a favore di Mac Os X, che batte sia Linux che Windows Vista...
Alcune considerazioni:
-Il mio Mac ha un processore piu' veloce di 260Mhz (cmq troppo pochi per giustificare il divario)
-Utilizzo Snow Leopard che di default fa partire la jvm a 64bit (e questo e' il motivo per il quale si mangia Linux)
Il confronto con Windows Vista rimane comunque impietoso.
Per quanto riguarda Flash e il link che hai postato, sarebbe interessante leggere i commenti; ne cito 2, se permetti:
"If you do a little research on Apple not letting Adobe access low-level hardware acceleration, the picture is this:
1. Adobe can access the exact same APIs as Apple uses in Safari. These wrap hardware acceleration in the CoreVideo API.
2. Apple doesn't allow anyone - not Safari, not Quicktime, not nobody - direct video acceleration access except through its APIs (which Safari and Quicktime use). The main reason for this is system stability (and a decade of graphics device drivers causing Windows to fall over the vast majority of the time bears this explanation out).
3. Flash doesn't use those APIs well the vast majority of the time "just in case" the Flash file might need to do random overlays in the middle of the video (ads etc), which are harder to do in the accelerated APIs without being able to "read back" the rendered pixels. Really, Adobe's complaints are that the APIs Apple provides don't include the read-back feature they have built their stack around. For what it's worth, Microsoft's APIs don't do this either, which is why Adobe did an end-run around the DirectX stack and petitioned all the graphics device driver vendors to add this feature to their drivers ... a feature which no one but Flash can use because it isn't a "stable" API."
"It was discussed in Daring Fireball, the blog of Apple technology pundit John Gruber.
Apple, Adobe and Flashh (http://daringfireball.net/2010/01/apple_adobe_flash)
Flash hardware accelerationn (http://daringfireball.net/2010/02/flash_hardware_acceleration)
Apple does have a way to let Flash have H.264 graphics acceleration via the Quicktime API, Adobe just refuses to go that way and wants to use lower-level APIs.
Gruber thinks it's a matter of proper software engineering and OS design if third-party plugins like Flash are limited to higher-level APIs and not directly interact with the underlying hardware.
Those links doesn't back up #3 in Tom Dibble's reply though, although I'm fairly certain it was discussed as well on other Apple and Adobe blogs."