--- Leon Rosenberg <[EMAIL PROTECTED]> wrote:
> Ok, my fault,
> read "page" and "java" in one sentence -> map to Java Page -> Java
> Server Page. Must be a circuit error in the brain.
> Anyway, does it mean, that a proper configured JVM on an opteron
> processor, will be significantly faster? Coul
Leon Rosenberg wrote:
Ok, my fault,
read "page" and "java" in one sentence -> map to Java Page -> Java
Server Page. Must be a circuit error in the brain.
Anyway, does it mean, that a proper configured JVM on an opteron
processor, will be significantly faster? Could be very interesting for
caches.
Ok, my fault,
read "page" and "java" in one sentence -> map to Java Page -> Java
Server Page. Must be a circuit error in the brain.
Anyway, does it mean, that a proper configured JVM on an opteron
processor, will be significantly faster? Could be very interesting for
caches...
Leon
On 4/3/06, Rai
Using large pages to eliminate TLB misses has nothing to do with the
size of the objects. From the view of the operating system java heap is
just a huge and continuous chunk of memory. Anything what's inside is
managed by the JVM. But whenever the JVM needs to access an adress it
needs to make
Hi,
recently I found (ok actually our sysadmin did) this articles on the
web, and wanted to share some thoughts.
http://www.devx.com/amd/Article/30529
http://www.devx.com/amd/Article/30785
The article describes, that using opteron and large memory pages can
give significant performance wins. I d
