Do you have a table/spec for the maximum and minimum size of the server (including all server side processes) and a "typical" client per OS and hardware architecture?
Thank you for the question. Please see below for a summary of the footprint size for both servers and client agents on various platforms. Also an example is provided at the bottom.
Distrix Server
Base memory usage is as follows:
Operating System
Memory Usage
Embedded
ROM 46KB, static RAM 35KB, dynamic RAM ~35 KB
Linux
7.5 MB, 5.75 MB shared
OS X
7.5 MB, 5.75 MB shared
Windows
9 MB
The Distrix server also allocates 32 bytes per client, plus the memory allocated by the selected communications protocol module which are:
FreeRTOS
64 bytes
Serial
2 KB
TCP/IP
2 KB
Distrix Client Libraries
Operating System
Memory Usage
Executable Size
Embedded
ROM 14 KB, static RAM 2 KB (minimum configuration ROM 9 KB, static RAM <2 KB)
14 KB
Linux
1.48 MB of memory including 850 KB of shared libraries
50 KB
OS X
1.48 MB of memory including 850 KB of shared libraries
50 KB
Windows
1.48 MB of memory including 850 KB of shared libraries
60 KB
Sample System
Operating System
Memory Usage
Executable Size
Embedded
512kb ROM, 64 Mbyte RAM
512 KB
We hope this answers your inquiry regarding the footprint of our solution. Further technical white papers are planned for Spring 2012, so be on the lookout in our documentation section for this material.
Please don't hesitate to inquire about other items that cross your mind.
Hello Greg,
Thank you for the question. Please see below for a summary of the footprint size for both servers and client agents on various platforms. Also an example is provided at the bottom.
Distrix Server
Base memory usage is as follows:
The Distrix server also allocates 32 bytes per client, plus the memory allocated by the selected communications protocol module which are:
Distrix Client Libraries
Sample System
We hope this answers your inquiry regarding the footprint of our solution. Further technical white papers are planned for Spring 2012, so be on the lookout in our documentation section for this material.
Please don't hesitate to inquire about other items that cross your mind.
Regards,
The Spark Support Team