Implemented Lazy Loading Feature #4308
Conversation
|
@FirePheonix i appreciate your contribution but i think we need to think more on this issue to get the best solution instead of just lazy loading we can do some more options as well like Batch Processing, Compression of JSON Data, Optimize Project Metadata, Browser Storage Alternatives, Implement Local Storage Management( I dont actually prefer this but saw someone mention this too) so @pikurasa i think we need to discuss about this and then try to move ahead |
|
@omsuneri While I was trying to solve the issue, I did look upon the following mentioned methods as well. I think lazy loading might be the best method in this case since we're trying to optimize the INITIAL loading time and we only want to access a small portion of data. |
Issue:
Earlier, MB was loading every single project file from IndexedDB into memory.
Improvises on: #4305
What does this PR do?
This PR documents the lazy loading mechanism implemented in the ProjectStorage,js class. Lazy loading ensures efficient memory usage by deferring the loading of project-specific data until it is explicitly required by the user itself.
How Lazy Loading Works
Initialization:
During the init method, only metadata (e.g., project IDs, current project ID) is restored. Full project data is not loaded.
Dynamic Data Fetching:
Methods like getCurrentProjectData and getCurrentProjectImage fetch project data dynamically from storage when accessed.
Example from getCurrentProjectData:
Caching for Reuse:
Once fetched, project data is cached in this.data.Projects for subsequent accesses, avoiding repeated storage queries.
How it helps
Optimized Memory: Only required data is loaded into memory.
Improved Performance: Reduces initialization time for large projects.
Scalability: Handles many projects efficiently.
Testing:
We'll have to test it in a computer with Lower GPU ALONG with where A LARGE NUMBER of projects (~500) are there.