Thank you for the link. I'll definitely have a look on it. But I'm not sure if it applies to TW. Somewhere I read that it loads all tiddlers into memory. I think this strategy explains the high memory consumption.
Am Freitag, 17. März 2017 17:31:06 UTC+1 schrieb PMario: > > On Friday, March 17, 2017 at 4:27:40 PM UTC+1, Mirko Clemente wrote: >> >> Same problem here. Without any tiddlers I measured 209M of memory >> consumption. I created some tiddlers and added 2 or 3 images and the node >> process consumed about 300M. That's a pity as my shared hosting is also >> limited to 500M. I am afraid that it won't take long to hit the limit. >> > > This may be of interest: > http://fiznool.com/blog/2016/10/01/running-a-node-dot-js-app-in-a-low-memory-environment/ > > > As it seems. node doesn't garbage collect until it hits any limits. So the > OS tools probably don't show the reality. > > -m > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/38c1c701-1c2e-458e-891e-a5a62e6abdf5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
