From b9c46f437bfd7be4af85a8f5ee0a1d24d1e073ef Mon Sep 17 00:00:00 2001 From: Richard Latham Date: Sat, 22 Jun 2019 17:07:31 -0400 Subject: [PATCH] Fix for #703 As discussed on #703, there is a dead link to the Oracle wiki. The [original page](http://web.archive.org/web/20150204134523/https://wikis.oracle.com/display/HotSpotInternals/CompressedOops) moved [here](https://wiki.openjdk.java.net/display/HotSpot/CompressedOops). --- 510_Deployment/50_heap.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/510_Deployment/50_heap.asciidoc b/510_Deployment/50_heap.asciidoc index ca6c08570..5af179762 100644 --- a/510_Deployment/50_heap.asciidoc +++ b/510_Deployment/50_heap.asciidoc @@ -74,7 +74,7 @@ is more wasted space simply because the pointer is larger. And worse than waste space, the larger pointers eat up more bandwidth when moving values between main memory and various caches (LLC, L1, and so forth). -Java uses a trick called https://wikis.oracle.com/display/HotSpotInternals/CompressedOops[compressed oops]((("compressed object pointers"))) +Java uses a trick called https://wiki.openjdk.java.net/display/HotSpot/CompressedOops[compressed oops]((("compressed object pointers"))) to get around this problem. Instead of pointing at exact byte locations in memory, the pointers reference _object offsets_.((("object offsets"))) This means a 32-bit pointer can reference four billion _objects_, rather than four billion bytes. Ultimately, this