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 bea3b96 Automatic Site Publish by Buildbot
bea3b96 is described below
commit bea3b96733c5db2aeed4c35fc11da628e5857a3f
Author: buildbot <[email protected]>
AuthorDate: Wed Jan 6 20:58:56 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 dfbd7f9..dce1d7a 100644
--- a/output/docs/Memory/MemoryPackage.html
+++ b/output/docs/Memory/MemoryPackage.html
@@ -535,9 +535,9 @@ 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>It is in these very large data environments that managing how the data gets
copied into RAM and
-when it is considered obsolete and can be written
-over by newer or different partitions of data is an important aspect of the
systems design.
+<p>In these very large data environments managing how the data gets copied
into RAM,<br />
+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.
For example, the Java specification requires that a new allocation of memory
be cleared before
it can be used. When the allocations become large this alone can result in
large pauses in a
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
