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

3D Tiles cache management #3808

Merged
merged 24 commits into from
Apr 12, 2016
Merged

3D Tiles cache management #3808

merged 24 commits into from
Apr 12, 2016

Conversation

pjcozzi
Copy link
Contributor

@pjcozzi pjcozzi commented Apr 6, 2016

3D Tiles now maintain a LRU cache of tiles to ensure only a maximum number of tiles, specified by the user, are loaded (unless more are needed to meet the SSE for the current view).

There's lots of interesting future work in the Cache Management section of the roadmap, #3241.

/**
* The corresponding node in the cache replacement list.
*
* @type {DoublyLinkedList}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DoublyLinkedListNode

@lilleyse
Copy link
Contributor

lilleyse commented Apr 7, 2016

That's all my comments. I like the approach here. Have you tried this on city datasets?

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Apr 11, 2016

I like the approach here. Have you tried this on city datasets?

Yes, Seattle and Washington DC.

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Apr 11, 2016

Updates based on review in de9b45a.

Let me know your thoughts on #3808 (comment)

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Apr 12, 2016

Updated in 515f3bd.

@lilleyse
Copy link
Contributor

Looks good!

@lilleyse lilleyse merged commit ec9a7e5 into 3d-tiles Apr 12, 2016
@lilleyse lilleyse deleted the 3d-tiles-cache branch April 12, 2016 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants