Hi PMario, That's definitely not the case. I've defined this server myself specifically for this. There is no competing load of any significance.
On Tuesday, October 7, 2014 3:46:53 PM UTC-4, PMario wrote: > > On Tuesday, October 7, 2014 3:23:48 PM UTC+2, Rick Williams wrote: >> >> The way I understand this is that we are simply forwarding the requests >> from nginx to the http server built in to the tiddlywiki program. >> > > jup. > > >> From the responses so far, I'm thinking there must be another way to >> configure this that I'm missing. I'm wondering where tiddlywiki actually >> stores the rendered html content. >> > > If you request a TW.html from the TW server, the TW server builds an html > file including the TW core, but without the "content" tiddlers. > The browser loads the core and makes a status request to the server > If status is ok, the core requests all the content tiddlers. > If the TW is loaded, the core makes the rendering .. so no communication > to the server > Only if you modify a tiddler, the content goes back and forth again. .. > > > The only idea I have, is, that the Data center sets the vm to "standby" if > there are no request for a longer time. > So the initial load could be starting the VM + app ... This could be up to > a minute. ... But I think, the server is in use. > > What about server load? > > -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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
