If I reduce the rate of updating the memory consumption will reduced?
If I want to run it as a daemon with the 1024mb what is the command
[solved]slow mobile front end
If I reduce the rate of updating the memory consumption will reduced?
If I want to run it as a daemon with the 1024mb what is the command
@temp just add start after pimatic.js;
node --max-old-space-size=1024 pimatic.js start
If it works i can modify the service for you so you can start it the normal way.
@temp said in slow mobile front end:
If I reduce the rate of updating the memory consumption will reduced?
Most likely
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@Gleno0h this message appears on the mobile Frontend now
Cannot GET /
If I start it with
sudo pimatic.js start
everything is fine
@temp what happens when yoi remove start?
Does pimatic crash with a stack trace error? Then increase 1024(idk how much pi3 can do)
2048 for example;
node --max-old-space-size=2048 pimatic.js
What does the debug say? it should boot normally
@mwittig debugging his page tells me the following;
Application Cache Error event: Manifest fetch failed (9)
Could that explain the lag?
I looked through his manifest and it is cached properly but not updated.
Anyone else using ssl have this error on chrome?
Allowing chrome to ignore invalid certificates doesnt solve the lag or the error.
One update.
I reinstalled my system from srketch. Now everything is really fluent and has a good performance memory consumption is about ~300mb. Then I tested the line from @Gleno0h and it’s was much better. Maybe it is good to use the whole memory from beginning? Or is there anything why this limitation to 512mb exists?
@temp good to hear! Running without ssl?
As to why node is limited, i dont know why.
Maybe it is required for the code, so they choose a safe value got multiple devices, idk.
If you want to integrate it you can add the line to the service /etc/init.d/pimatic
Sorry but there is no script /etc/init.d/pimatic
@temp then you didnt install as a service :-D
https://pimatic.org/guide/getting-started/autostarting/
Do I need to remove it from the update.d first? And add it again? Or simply edit the file?
@temp nah, just update it;
sudo update-rc.d pimatic defaults
I added
if [ "$1" = "start" ] || [ "$1" = "stop" ] || [ $
then
node --max-old-space-size=1024 pimatic.js $1
exit "$?"
But get this error now
$ sudo service pimatic start
Job for pimatic.service failed. See 'systemctl status pimatic.service' and 'journalctl -xn' for details.
Yes full path is required.
Closed
@temp but in the end, did you disable ssl? Because there was a certificate issue so the cache did not update. I, and maybe others want to know if that could have broken your cache somehow. IF you use ssl again, could you look into the console (chrome F12) if the error is gone that i mentioned earlier?
How do I see if the error is gone with f12 in chrome sorry never used it
@temp if your details are still the same, ill look this weekend. PM the url and login if it has changed.
I still get the manifest error.
What is the cause of the manifest error? Do I need to write https://xxxxxxx.ddns.net I’m the hostname configuration during SSL generating? Or what?
Can someone from the @developer help?
@temp i think error 9 is there because it is a self-signed certificate. If you would get an official certificate it would be gone so i think it is safe to say that error 9 does not matter and would not reduce any performance. It is just a safety check to prevent a man-in-the-middle attack. There is a command floating around to prevent this, it did not work for me.