This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datasketches-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new c26f8a5 Automatic Site Publish by Buildbot
c26f8a5 is described below
commit c26f8a50b8ae4f2fce4095278a8e3d94d9d1f55f
Author: buildbot <[email protected]>
AuthorDate: Wed Jan 6 22:04:45 2021 +0000
Automatic Site Publish by Buildbot
---
output/docs/Memory/MemoryPackage.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/output/docs/Memory/MemoryPackage.html
b/output/docs/Memory/MemoryPackage.html
index dce1d7a..243bc2b 100644
--- a/output/docs/Memory/MemoryPackage.html
+++ b/output/docs/Memory/MemoryPackage.html
@@ -535,7 +535,7 @@ which can even be orders of magnitude larger.
How the system designers select the partitions of the data to be in RAM over
time is quite complex
and varies considerably based on the specific objectives of the systems
platform.</p>
-<p>In these very large data environments managing how the data gets copied
into RAM,<br />
+<p>In these very large data environments managing how the data gets copied
into RAM,
when it is considered obsolete, and when it can be written
over by newer or different partitions of data, are important aspects of the
systems design.
Having the JVM manage these large chunks of memory is often problematic.
@@ -550,9 +550,9 @@ memory directly.</p>
<p>The JVM has a very sophisticated heap management process and works very
well for many
general purpose programming tasks.
However, for very large systems that have critical latency requirements,
-utilizing off-heap memory becomes a requirement.</p>
+utilizing off-heap memory efficiently becomes a requirement.</p>
-<p>Java does not permit normal java processes direct access to off-heap
memory. Nonetheless,
+<p>Java does not permit normal java processes direct access to off-heap memory
(except as noted below). Nonetheless,
in order to improve performance, many internal Java classes leverage a
low-level, restricted
class called (unfortunately) “<em>Unsafe</em>”, which does exactly that. The
methods of <em>Unsafe</em>
are native methods that are initially compiled into C++ code. The JIT compiler
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
