Baseflow / Baseflow/flutter_cached_network_image

memory requirements

Open
#712 3 comments 3 reactions 0 assignees View on GitHub
Dominant language
Dart
Stars
2.6k
Forks
731
Avg merge
3d 9h
Merged PRs (30d)
1

Description

We found that the memory increases significantly when there are a large number of instantaneous requests. Can the upper layer process the maximum number of requests through the queue when loading images, and remove the excess from the queue? cached_network_image will depend on flutter_cache_manager, and the queue of flutter_cache_manager cannot actually solve the instantaneous large number of requests. At present, our processing is: before using cached_network_image, through queue management (it will monitor whether the image is loaded), set the maximum number of simultaneous requests, and reject the most advanced request when it exceeds. After this processing, the memory performance is significantly reduced. I wonder if the developers of cached_network_image can handle this requirement?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.