From 56746f2f189d0d4f0e282ef4ef1428cf4bfec6cd Mon Sep 17 00:00:00 2001 From: Lauri Ojansivu Date: Sun, 30 Jun 2019 15:10:01 +0300 Subject: [PATCH] Updated Raspberry Pi (markdown) --- Raspberry-Pi.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Raspberry-Pi.md b/Raspberry-Pi.md index b538369..2e9ce7e 100644 --- a/Raspberry-Pi.md +++ b/Raspberry-Pi.md @@ -14,10 +14,12 @@ mongorestore --drop --noIndexRestore ``` Wekan on RasPi3 -When using Firefox on network laptop (Core 2 Duo laptop, 8 GB RAM, SSD harddisk) to browse RasPi Wekan server, small boards load at about 3 seconds at first time. When loading, node CPU usage goes to about 100%. MongoDB CPU usage stays low, sometimes goes to 18%. This is because indexes has been added to Wekan MongoDB database. Loading my biggest Wekan board at first time takes 45 seconds, and next time takes about 2 seconds, because data is at browser cache. When Wekan browser tab is closed, node CPU usage drops 4-23%. +When using Firefox on network laptop (Core 2 Duo laptop, 8 GB RAM, SSD harddisk) to browse RasPi Wekan server, small boards load at about 3 seconds at first time. When loading, node CPU usage goes to about 100%. MongoDB CPU usage stays low, sometimes goes to 18%. This is because indexes has been added to Wekan MongoDB database. Loading my biggest Wekan board at first time takes 45 seconds, and next time takes about 2 seconds, because data is at browser cache. When Wekan browser tab is closed, node CPU usage drops 4-23%. There is no errors given by Wekan at RasPi3, RasPi3 arm64 behaves similar to x64 server that has 1 GB RAM. Wekan on RasPi3 +I did also test Wekan arm64 on arm64 bare metal server, same Wekan bundle worked there. + ### Download .7z size 876 MB, unarchived RasPi3 .img size of 4.5 GB. At first boot disk image expands to full SD card size.