Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Smarter handling of cached resources #25

Closed
ksons opened this issue Oct 29, 2013 · 1 comment
Closed

Smarter handling of cached resources #25

ksons opened this issue Oct 29, 2013 · 1 comment

Comments

@ksons
Copy link

ksons commented Oct 29, 2013

Currently the XHR request gets cached as it could be reused in structured file formats that allow to adress multiple objects within one resource. However, the cached responses claim a lot of memory.

The desired behaviour:

  1. Don't cache responses for unstructured file formats (e.g. OpenCTM, xml3d-json)
  2. Add heuristic that manages freeing the response for structured resources. A simple one could be to free the resources once there is no request in the queue that requires the resource. Another options include using a LRU or LFU strategy
@ksons
Copy link
Author

ksons commented Nov 18, 2013

Since 4.5, the resource manager does not cache the raw XHR response but the processed data in whatever the format handler thinks is most suitable. This saves a lot of memory, particular for JSON and XML request, where the XHR is quite memory consuming.

However, unused resources are not yet detected and remain cached. I opened Issue #27 for this.

@ksons ksons closed this as completed Nov 18, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant