21.10.2020, 17:52
I know that from a few years there is a memory limitation and this is not possible to have too many trends. Earlier I had LM LB and on it I had >400 trends with 5min resolution and 2 years of full resolution data.
Unfortunately it is not possible to repair it because it is not supported but current LMs are really too limited in this subject. Yesterday I've tried add few trends to LM5 Reactor IO V2 (i.MX6) and with same setting I can save only 13 trends and I have 88% disk used. I see that probably trends are storaged on /dev/mtdblock0 which have only 20MB. I know that this storage is probably very safe and reliable but I think good direction would be to add to Trend storage destination because some not so important trends could be storaged on /dev/mmcblk0p3 where is 3.2GB free space
For me currently still there is a lack of something like LM Load Balancer. Sometimes I must divide functions between different LMs like in case trends which is bad because then it is not possible to freely comparing different trends but only trends from one LM. Same with scripts. Theoretically it is possible to divide e.g. systems between different LMs e.g. HVAC, Blinds etc. but practically then you must send unnecessary telegrams to the bus to stay synced in both ways and code is unnecessarily splitted.
Unfortunately it is not possible to repair it because it is not supported but current LMs are really too limited in this subject. Yesterday I've tried add few trends to LM5 Reactor IO V2 (i.MX6) and with same setting I can save only 13 trends and I have 88% disk used. I see that probably trends are storaged on /dev/mtdblock0 which have only 20MB. I know that this storage is probably very safe and reliable but I think good direction would be to add to Trend storage destination because some not so important trends could be storaged on /dev/mmcblk0p3 where is 3.2GB free space
For me currently still there is a lack of something like LM Load Balancer. Sometimes I must divide functions between different LMs like in case trends which is bad because then it is not possible to freely comparing different trends but only trends from one LM. Same with scripts. Theoretically it is possible to divide e.g. systems between different LMs e.g. HVAC, Blinds etc. but practically then you must send unnecessary telegrams to the bus to stay synced in both ways and code is unnecessarily splitted.
Done is better than perfect
