[openstreetmap/openstreetmap-website] Reduce size of application.js by removing translations? (#1949)
notifications at github.com
Thu Aug 16 12:24:37 UTC 2018
> I don't know whether there's a direction of travel or not, and I don't have a strong opinion on that. But in my investigations so far it appears that buildling small html pages client-side has moderately large downsides. Again it might not be so noticeable on fast connections in Europe, but when a simple browse page takes multiple EU <-> HK roundtrips it becomes noticeable to me - even on a high bandwidth connection. I expect it will be much worse on low-bandwidth, high-latency connections elsewhere.
Well surely the point is that we're not really building them client side - we are fetching them from the server and then augmenting. If they were truly built on the client (as horrible as that is to write) then there wouldn't be multiple round trips.
> I don't think putting together the browse or query pages server-side will actually be that expensive, but that's definitely a risk. From what I've seen so far, making one request and getting the compact html in response is going to be much better than multiple xhr back-and-forwards and large json payload responses.
My concern is not CPU or anything but rather tying up a rails server for N seconds while it waits for an API response. Obviously one solution is to spin up more rails server, subject to memory constraints.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rails-dev