I’m pretty sure .world being slow is a web frontend problem. It often takes forever to load in my browser, but the same content loads quickly in the Voyager Android app.
I should probably try the several alternative web UIs they have available to see if they’re faster than the default one, but I can’t be bothered to walk over to my desktop PC right now.
It can’t be the backend because it’s got to query the same data whether it’s feeding the web UI or Voyager, so that wouldn’t explain the vast loading time differences between them. If the backend were slow they would both be slow, but Voyager’s load times are great.
I’m pretty sure .world being slow is a web frontend problem. It often takes forever to load in my browser, but the same content loads quickly in the Voyager Android app.
I should probably try the several alternative web UIs they have available to see if they’re faster than the default one, but I can’t be bothered to walk over to my desktop PC right now.
The XHR requests are taking forever to load. This implies backend APIs are the culprit.
If it were backend, Voyager would be slow too because it’s requesting the same data.
Maybe Voyager connects to the backend using something other than XmlHttpRequest.
@cm0002 @grue Maybe, but backend / database load is more likely, isn’t it ?
You can look at your browser developer tools and see downloads sizes, durations, where CPU time is used on client side ;)
It can’t be the backend because it’s got to query the same data whether it’s feeding the web UI or Voyager, so that wouldn’t explain the vast loading time differences between them. If the backend were slow they would both be slow, but Voyager’s load times are great.