Hi Benjamin,
Thanks for sharing the footprint data. A couple of quick follow-up questions: can you share what is the benchmark used for this study ? Also, is there a
way to quantify the OSGi footprint cost distinctly, when you measure the VM/Runtime footprints ?
From: kura-dev-bounces@xxxxxxxxxxx [mailto:kura-dev-bounces@xxxxxxxxxxx]
On Behalf Of Benjamin Cabé
Sent: Friday, May 13, 2016 10:53 AM
To: kura-dev@xxxxxxxxxxx
Subject: [kura-dev] Eclipse Kura footprint
A couple weeks ago I did run some tests to get a sense of the actual footprint of Eclipse Kura on a system, and more specifically requirements in terms of disk
space, RAM, as well as some figures on the "cold" startup time (I.e from "Kura not running", to "all Kura default services up and running").
I have to admit I was positively surprised about the fact that the overhead some might expect from Java-based runtimes is actually not that much of an issue,
I would say, for the kind of devices Eclipse Kura targets.
Please feel free to amend the Wiki page with comments, or add info regarding other h/w platforms or runtimes.
|
Eclipse Kura
|
Node-RED
|
VM
|
JVM
|
Node.JS
|
VM footprint (disk)
|
~15 MB (Oracle JVM compact2)
|
43 MB (node-v5.9.1)
|
Runtime footprint (disk)
|
44 MB (Kura 1.4)
|
62 MB
|
Total footprint (disk)
|
59 MB
|
105 MB
|
Startup time (on Rasp. Pi 3)
|
~8 sec
|
~5 sec
|
Memory footprint (RAM)
|
< 20 MB
|
22 MB
|
Benjamin Cabé – IoT Evangelist
Eclipse Foundation
+33 (0) 619196101
@kartben