Check SPipes memory issues at CSAT planning deployment

[blcham]

A/C:

• compare memory footage to other docker services
• compare memory footage if you restart the service (docker-compose -f ..-dev.yml restart s-pipes-engine)
• list commands on how to get memory footage of docker service

[Matthew-Kulich]

Compare memory footage to other docker services

Name	Memory usage (31GB max)
csat-planning-s-pipes-engine (before restart)	10%
msmt-fta-fmea-converter	9.16%
graphdb	5.68%
csat-planning-s-pipes-engine (after restart)	4.89%
csat-planning-elasticsearch	4.47%
csat-planning-dashboard	4.19%
19msmt-distribution_fta-fmea-server_1	2.50%
aircraft-maintenance-planning	2.43%
others	<=1%

---

Compare memory footage if you restart the service

• before the restart 10%
• 1 minute after the restart 5% memory
• one hour after the restart still 5% memory
• one day after the restart 11 % memory

---

List commands on how to get memory footage of docker service

• The best command by far is the docker stats

@blcham

[blcham]

docker stats after couple days:

[blcham]

My investigation:

Set-up	Memory usage
csat s-pipes within docker	1.48GiB
csat s-pipes without nlp+other modules within docker	1.431GiB
s-pipes engine without nlp+other modules within docker with s-pipes modules	896.6MiB
s-pipes engine without nlp+other modules within docker	875.1MiB
docker run tomcat:9.0-jdk8-slim	118.8MiB