Java performance: cache-sensitive Java programming

• Autores: Glen McCluskey
• Localización: ;login:: the magazine of USENIX & SAGE, ISSN 1044-6397, Vol. 25, Nº. 8, 2000, págs. 24-26
• Idioma: inglés
• Texto completo no disponible (Saber más ...)
• Resumen

  • One of the sayings you may have heard in connection with Java programming is �write once, run anywhere.� The idea is that Java programs are compiled into an intermediate bytecode form, and then interpreted or dynamically compiled by the Java Virtual Machine (JVM). A further aspect of this idea is that a Java application is insulated from the underlying operating system and hardware.

    This approach is a �good thing� and is at least partially true in practice. For example, it�s possible to take a bytecode (.class) file produced by one Java compiler, and use that file with a JVM that comes from somewhere else.

    But it�s also interesting to explore the limitations of this approach. For example, if you�re a Java programmer, do you ever need to worry about the characteristics of particular hardware that your application may run on? In this column, we�ll look at a specific example, one that involves cache-sensitive programming