You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, TiddlyServer seems to start a new server.js instance for every wiki, which can quickly eat up available memory if you have more than a handful of wikis.
I would prefer it if either:
TiddlyWiki instances are started and stopped automatically depending on whether they're in use or not.
Wikis in the directory listing feature a manual toggle button next to them, to start and stop the instances when needed.
In addition: I have 4 wikis in my directory, but htop shows 10 instances of server.js with 1342MB virtual memory and 336MB physical memory each. Is this expected behavior?
The text was updated successfully, but these errors were encountered:
There will only ever be one active instance of server.js. TiddlyServer does not spawn new processes -- it loads all the TiddlyWikis into one process and distributes the requests to the respective Javascript objects accordingly. I've also designed it to be reasonably fast to start, so you can always just restart it as long as there are no pending saves on the server side (a few seconds of inactivity should allow all saves to finish).
At the moment, TiddlyServer seems to start a new server.js instance for every wiki, which can quickly eat up available memory if you have more than a handful of wikis.
I would prefer it if either:
In addition: I have 4 wikis in my directory, but htop shows 10 instances of server.js with 1342MB virtual memory and 336MB physical memory each. Is this expected behavior?
The text was updated successfully, but these errors were encountered: