You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I checked my web browser's DevTools panel (i.e., its "Network" tab), I saw that there were two HTTP request/response cycles that took 10+ seconds each, happened serially rather than in parallel, and which blocked the UI from being displayed.
I briefly discussed this with @naglepuff in passing today and he suggested something that I am in favor of, which is: assuming we have to fetch data from these URLs, update the Data Portal client (code) to display spinners on the specific UI elements that depend on the fetched data. In addition, update the Data Portal client (code) to (a) not block on those fetches — proceed to show the UI while the fetches are happening; and (b) do the fetches in parallel, not in serial.
The text was updated successfully, but these errors were encountered:
When I visited this URL on my local machine, the page took 40 seconds to load: https://data.microbiomedata.org/details/study/nmdc:sty-11-prtb4s28
When I checked my web browser's DevTools panel (i.e., its "Network" tab), I saw that there were two HTTP request/response cycles that took 10+ seconds each, happened serially rather than in parallel, and which blocked the UI from being displayed.
The requests were to:
I briefly discussed this with @naglepuff in passing today and he suggested something that I am in favor of, which is: assuming we have to fetch data from these URLs, update the Data Portal client (code) to display spinners on the specific UI elements that depend on the fetched data. In addition, update the Data Portal client (code) to (a) not block on those fetches — proceed to show the UI while the fetches are happening; and (b) do the fetches in parallel, not in serial.
The text was updated successfully, but these errors were encountered: