Skip to content
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.

Find ways to improve the initial loading of Change.json #16

Open
achimcc opened this issue Sep 25, 2021 · 0 comments
Open

Find ways to improve the initial loading of Change.json #16

achimcc opened this issue Sep 25, 2021 · 0 comments
Labels
priority-low size-sm TypeScript Issue requires TypeScript/React coding

Comments

@achimcc
Copy link
Contributor

achimcc commented Sep 25, 2021

In the prototype, the ink! dependencies which are contained ion the Change.json file are received by calling fetch() to obtain them from the Netlify server after the initial page-load. This can take up to 2 min. Are there ways to improve the loading speed, like:

  • Load them from another server?
  • Split the file into multiple smaller files?
  • Stream the .json file
  • Directly subscribe to stream of JSON data instead of transferring file(-s)?

The Change.jsonm file is currently fetched, however, it is approx. 50 MB big (~5MB gzipped teransfer volume). It is probably not cached for long due to its size? Are there ways to more persistently cache this data?

Another approach whhcihs should be considered to improve the performance of loading and applying the Change.json file, is to fetch the data through Comlink Webworkers and to pass them to another Webworker thread which executes rust analyzer, see e.g.:

https://issueexplorer.com/issue/GoogleChromeLabs/comlink/450

@achimcc achimcc added size-sm TypeScript Issue requires TypeScript/React coding labels Sep 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority-low size-sm TypeScript Issue requires TypeScript/React coding
Projects
None yet
Development

No branches or pull requests

1 participant