I agree, the behavior on playground is usable, although still not perfect. To be honest, if it didn’t show the spinner when the load time is < 100ms or something, it would probably “feel” more seamless.
It is possible there is additional latency going to my AWS instance for some reason. According to the Page Index, there are 239 pages total in the wiki. From my xwiki.cfg:
#-# Maximum number of documents to keep in the cache. #-# The default is 500. # xwiki.store.cache.capacity=500
Is there a way to tell if the server cache is saturated? I know very little about Java. I will say, on a reboot, XWiki takes several minutes to start up, and only after the first attempt at a page view. I assumed that was XWiki caching stuff. Not sure if this is helpful, but a quick peak at free memory:
$ cat /proc/meminfo MemTotal: 2046536 kB MemFree: 134408 kB MemAvailable: 868540 kB Buffers: 262932 kB Cached: 444620 kB SwapCached: 0 kB
Should I start a new topic for this conversation? It seems like there are two threads: one, can the Navigation Panel be made to be more robust; two, is there a degenerate case with re: performance on AWS t2.small instances.