edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject Re: Small (memory) footprint specifics
Date Fri, 29 Dec 2017 22:05:55 GMT
Unfortunately I can't provide you with such data as I am just getting started in using Edgent
in real applications. Maybe Dale might help you with that.

Chris

Outlook for Android<https://aka.ms/ghei36> herunterladen

________________________________
From: Otis Gospodnetić <otis.gospodnetic@gmail.com>
Sent: Friday, December 29, 2017 10:36:21 PM
To: dev@edgent.apache.org
Subject: Re: Small (memory) footprint specifics

Hi Chris,

Thanks for the quick reply!
3.9 MB heap (was the RSS also cca 4 MB?) is much smaller than I anticipated
given this is running in the JVM.  What's the trick? :)

I assume that DevelopmentSample app is the one from
https://github.com/apache/incubator-edgent-samples/tree/develop/topology/src/main/java/org/apache/edgent/samples/topology
?

How much bigger might the memory footprint be if one ran a more realistic
app, say something that:
* get data from JMX (so RMI involved) or calls some HTTP API that returns
JSON (so parsing needed)
* labels/tags data (like in the
https://github.com/apache/incubator-edgent-samples/blob/develop/topology/src/main/java/org/apache/edgent/samples/topology/StreamTags.java
)

... but still no windowed analysis on the agent side.

Are we then talking 10-20-30+ MB?

Thanks,
Otis
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/


On Fri, Dec 29, 2017 at 2:38 PM, Christofer Dutz <christofer.dutz@c-ware.de>
wrote:

> Hi Otis,
>
> So, I just ran the DevelopmentSample application in JProfiler and it took
> a minimum of 3,9MB of heap … This however is neither a very representative
> Example, but it should demonstrate that you don’t need a lot of memory to
> run an Edgent application. I guess it also depends highly on the type of
> operations. If you use a lot of Windowed analysis, I would expect the
> memory requirements to be a lot higher than when using only pure stream
> operations that don’t require keeping events in memory.
>
> Chris
>
> Am 29.12.17, 17:29 schrieb "Otis Gospodnetić" <otis.gospodnetic@gmail.com
> >:
>
>     Hi,
>
>     This is from the FAQ:
>
>     *Edgent is designed for the edge. It has a small footprint, suitable
> for
>     running on constrained devices.*
>
>     Can anyone share some specifics of that "small footprint" part in
> terms of
>     memory?  How small of a footprint can Edgent have?
>
>     Thanks,
>     Otis
>     --
>     Monitoring - Log Management - Alerting - Anomaly Detection
>     Solr & Elasticsearch Consulting Support Training -
> http://sematext.com/
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message