You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stratos.apache.org by bu...@apache.org on 2014/05/20 11:28:20 UTC
svn commit: r909385 - in /websites/staging/stratos/trunk/content: ./
about/why-apache-stratos.html
Author: buildbot
Date: Tue May 20 09:28:20 2014
New Revision: 909385
Log:
Staging update by buildbot for stratos
Modified:
websites/staging/stratos/trunk/content/ (props changed)
websites/staging/stratos/trunk/content/about/why-apache-stratos.html
Propchange: websites/staging/stratos/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 20 09:28:20 2014
@@ -1 +1 @@
-1596160
+1596161
Modified: websites/staging/stratos/trunk/content/about/why-apache-stratos.html
==============================================================================
--- websites/staging/stratos/trunk/content/about/why-apache-stratos.html (original)
+++ websites/staging/stratos/trunk/content/about/why-apache-stratos.html Tue May 20 09:28:20 2014
@@ -156,6 +156,9 @@
<h2>Predicting future loads</h2>
<p>Another important capability of Apache Stratos is predicting immediate future load, based on current health statistics. All cartridges, Load balances, health monitors are publishing health status into CEP (Complex Event Processor) via real time event bus. CEP will aggregate all these events and calculate first derivative, second derivative for a given time window frame and paas resulting streams to Auto scaler via reliable message bus.</p>
<p>Auto Scaler used motion equation to get immediate (next minute) future load.</p>
+<span>s = ut+ 1/2 at<sup>
+
+2</sup></span>
</article>
</section>
</div>