Linked by Thom Holwerda on Thu 20th Mar 2008 21:34 UTC
Thread beginning with comment 305911
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2006-01-11
Certainly a JIT approach can be useful if you've got a machine around and you want to run a non-native app. But it's never going to be a first-choice option, it's more like an option you would choose if you're stuck with an incompatible processor or an incompatible app. Native execution is always going to be better, unless you have an app for such an old architecture that, even with the JIT performance penalty, your new machine can still run it faster.
And that might even be the case for your old Solaris/SPARC apps. We've got plenty of old, underpowered SPARC hardware around here.