- FAQs: edgeEngine memory & CPU usage
FAQs: edgeEngine memory & CPU usage
How much memory does edgeEngine take to run?
Baseline memory usage with no services running
What are the Guidelines for how memory usage may grow as additional services are deployed?
As a result of the characteristics inherent to serverless microservices, the microservice instances are exclusively executed upon receiving RESTful API requests. In the absence of requests, the memory is released. The memory allocation expands proportionally to the runtime heap required by each microservice. A minimum of 2MB of heap memory is needed for each microservice, encompassing the loading of the microservice image into memory.
How much CPU does edgeEngine take to run?
Baseline CPU usage when idle and not handling any service traffic
Guidelines for how the CPU usage may grow as additional services are deployed
Due to the inherent characteristics of serverless microservices, the microservice instance is invoked solely in response to RESTful API requests, resulting in a slight increase in CPU usage for the duration of the request.
How much disk space does the edgeEngine take to run?
Baseline disk usage for just edgeEngine and its supporting tools and libraries
edgeEngine incorporates statically linked libraries, resulting in a complete binary size of less than 8MB.
What are the Guidelines for how the disk usage may grow as additional services are deployed
The disk consumption of edgeEngine is directly linked to the number of deployed serverless microservices. The size of each serverless microservice image can range from as large as 1MB to as small as 100KB.
Each individual microservice can additionally utilize database and disk space, which may exhibit varying degrees of utilization.