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/mahout.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1024950 Automatic Site Publish by Buildbot
1024950 is described below
commit 1024950a3e939723d8934ceea5cb9fb0485cdb3d
Author: jenkins <[email protected]>
AuthorDate: Fri Jan 18 18:58:35 2019 +0000
Automatic Site Publish by Buildbot
---
feed.xml | 2 +-
general/mahout-benchmarks.html | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/feed.xml b/feed.xml
index 78a371a..c110b30 100644
--- a/feed.xml
+++ b/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed
xmlns="http://www.w3.org/2005/Atom"; ><generator uri="https://jekyllrb.com/";
version="3.5.0">Jekyll</generator><link
href="http://mahout.apache.org//feed.xml"; rel="self"
type="application/atom+xml" /><link href="http://mahout.apache.org//";
rel="alternate" type="text/html"
/><updated>2019-01-18T18:14:45+00:00</updated><id>http://mahout.apache.org//feed.xml</id><title
type="html">Apache Mahout</title><subtitle>Distributed Linear
Algebra</subtitle> [...]
+<?xml version="1.0" encoding="utf-8"?><feed
xmlns="http://www.w3.org/2005/Atom"; ><generator uri="https://jekyllrb.com/";
version="3.5.0">Jekyll</generator><link
href="http://mahout.apache.org//feed.xml"; rel="self"
type="application/atom+xml" /><link href="http://mahout.apache.org//";
rel="alternate" type="text/html"
/><updated>2019-01-18T18:58:01+00:00</updated><id>http://mahout.apache.org//feed.xml</id><title
type="html">Apache Mahout</title><subtitle>Distributed Linear
Algebra</subtitle> [...]
<p>This release might not seem super exciting from a user perspective
(except
we’re bumping Apache Spark to version 2.x and Scala to version 2.11) but
diff --git a/general/mahout-benchmarks.html b/general/mahout-benchmarks.html
index 044740c..040a232 100644
--- a/general/mahout-benchmarks.html
+++ b/general/mahout-benchmarks.html
@@ -301,7 +301,7 @@ processing – that’s really the appropriate solution.</p>
<p>This shows you can still tackle fairly impressive scale with a
non-distributed solution. These results suggest that the largest instances
-available from EC2 would accomodate almost 1 billion ratings in memory.
+available from EC2 would accommodate almost 1 billion ratings in memory.
However at that scale running a user’s full recommendations would easily be
measured in seconds, not milliseconds.</p>
