Data description for 64Mb swapfile for the filesystem:
dd if=/dev/zero of=/tmp/log/cmh/swapfile bs=1024 count=65536
Creating the actual swapfile:
mkswap /tmp/log/cmh/swapfile
Start using the newly created swapfile:
swapon /tmp/log/cmh/swapfile
It appears the swap file does not persist between reboots.
My questions are:
1)-> Can the “swapon /tmp/log/cmh/swapfile” statement be added to the Vera Startup? How?
2)-> Is there any reason or danger in using the swap file. I pursued this as I have 70 some devices, 15 cameras on the system. It is very slow and the FREE cmd shows very little memory.
Memory currently is:
total used free shared buffers
Mem: 30540 30228 312 0 384
Swap: 0 0 0
Total: 30540 30228 312
3)-> Am I approaching/exceeding the practical limitation of devices on Vera2?
So basically you just have to add your swapon command to this file.
If I got that right one of the biggest concern is the limited read/write cycles for an usb stick. Using SWAP on usb will eventually kill the stick, but up to now I had no problems.
It is more or less the plugins that will cause Vera 2 to use memory. You should be OK with 70 or so devices. Once you start adding many cameras and other plugins, that is when Vera 2 can become slow.
Is the use of a single plugin for the camera the memory penalty or the number of cameras. All are of the same type, using the built in generic camera support of UI5.
I removed 4 cameras without measurable impact on available memory. Or would I need to remove all cameras?
Would upgrading to vera3 resolve the low memory, slow performance issues?