Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Toggling Wiki Instances #81

Open
ConorLPBoyle opened this issue Feb 25, 2020 · 1 comment
Open

Toggling Wiki Instances #81

ConorLPBoyle opened this issue Feb 25, 2020 · 1 comment

Comments

@ConorLPBoyle
Copy link

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?

@Arlen22
Copy link
Owner

Arlen22 commented Feb 26, 2020

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants