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 66c47686 Automatic Site Publish by Buildbot
66c47686 is described below
commit 66c476864ebd3b74f56ca2e5bf2017bc36a42446
Author: buildbot <[email protected]>
AuthorDate: Tue May 3 00:40:21 2022 +0000
Automatic Site Publish by Buildbot
---
output/docs/Architecture/SketchCriteria.html | 6 +++---
output/docs/Architecture/SketchesByComponent.html | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/output/docs/Architecture/SketchCriteria.html
b/output/docs/Architecture/SketchCriteria.html
index 460a0f8b..bf9e70ac 100644
--- a/output/docs/Architecture/SketchCriteria.html
+++ b/output/docs/Architecture/SketchCriteria.html
@@ -513,17 +513,17 @@
<p>There are lots of clever and useful algorithms that are sometimes called
“sketches”. However, due to limited resources, in order to be included in the
DataSketches library, we had to clearly define what we meant by the term
“sketch”. Otherwise, we would end up with a hodge podge of algorithms and have
to answer: Why don’t we include algorithm X?.</p>
-<p>In order to be in our library, a <em>Sketch</em> must exhibit these
properties:</p>
+<p>In order to be in our library, a <em>Sketch</em> should exhibit these
properties:</p>
<h2 id="streaming--one-touch">Streaming / One-Touch</h2>
-<p>Sketches are a class of streaming algorithms by definition, which means
they only touch or process each item in a stream once. This is absolutely
required for real-time applications.</p>
+<p>Sketches are a class of streaming algorithms by definition, which means
they only touch or process each item in a stream once. This is absolutely
essential for real-time applications.</p>
<h2 id="small-in-size">Small in Size</h2>
<p>One of the key properties of any sketch is that it is a synopsis or summary
of a much larger data set. The whole point of a small summary is that it is
faster to read and merge. In this context, <em>small</em> means small with
respect to the original data. If the original data is terabytes in size, a
single sketch of 100KB may not seem very different from a sketch of 50KB as
both are very small compared to the original data.</p>
<p>But <em>small</em> can also be important in an systems context. If that
original terabyte of data generates 10,000 sketches, each sketch consuming
100KB, that amounts to a GB of storage. Now the total memory use starts to be
a concern. Being able to reduce that by 50% by using a smaller (and otherwise
equivalent) sketch can be a big deal.</p>
-<p>Nonetheless, <em>small</em> is relevant to the specific application.
Sketches can very from a few bytes to many megabytes depending on the specific
sketch and how it has been configured. Whether it is small enough is up to the
system engineers to determine.</p>
+<p>Nonetheless, <em>small</em> is relevant to the specific application.
Sketches can very from a few bytes to many megabytes depending on the specific
sketch and how it has been configured. Whether it is small enough depends on
the use-case and the specific environment.</p>
<h2 id="sublinear-in-size-growth">Sublinear in Size Growth</h2>
<p>Not only should a sketch start small, it needs to stay small as the size of
the input stream grows. Some sketches have an upper bound of size independent
of the size of the input stream, which clearly makes them sublinear. Other
sketches may need to continue to increase their size as the stream grows. For
these sketches it is important that they do so very very slowly. They should
grow sublinearly by no more then <em>O(log(n))</em> or preferrably by <em>O(k
log(n/k))</em> or less.</p>
diff --git a/output/docs/Architecture/SketchesByComponent.html
b/output/docs/Architecture/SketchesByComponent.html
index e3ef9cbd..120d652f 100644
--- a/output/docs/Architecture/SketchesByComponent.html
+++ b/output/docs/Architecture/SketchesByComponent.html
@@ -560,11 +560,11 @@ This code is versioned and the latest release can be
obtained from
</tr>
<tr>
<td>org.apache.datasketches.kll</td>
- <td>Quantiles sketch with better accuracy per size than the standard
quantiles sketch. Includes PMF, CDF funtions, for floats. Only on-heap.</td>
+ <td>Quantiles sketch with better accuracy per size than the standard
quantiles sketch. Includes PMF, CDF functions, for floats, doubles. On-heap
& off-heap.</td>
</tr>
<tr>
<td>org.apache.datasketches.quantiles</td>
- <td>Standard Quantiles sketch, plus PMF and CDF functions, for doubles
and generics and for heap and off-heap.</td>
+ <td>Standard Quantiles sketch, plus PMF and CDF functions, for doubles
and generics. On-heap & off-heap.</td>
</tr>
<tr>
<td>org.apache.datasketches.req</td>
@@ -576,7 +576,7 @@ This code is versioned and the latest release can be
obtained from
</tr>
<tr>
<td>org.apache.datasketches.theta</td>
- <td>Unique counting Theta Sketches for both heap and off-heap</td>
+ <td>Unique counting Theta Sketches for both on-heap & off-heap</td>
</tr>
<tr>
<td>org.apache.datasketches.tuple</td>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
