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

Tweet Load Memory Issue #12

Open
Yicong-Huang opened this issue Oct 14, 2019 · 5 comments · Fixed by #13
Open

Tweet Load Memory Issue #12

Yicong-Huang opened this issue Oct 14, 2019 · 5 comments · Fixed by #13
Assignees
Labels

Comments

@Yicong-Huang
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The current design, all tweets are fetched to frontend and let the frontend tweet.layer to handle data slicing and display, which consumes almost all available memory on frontend.

Describe the solution you'd like
two step loading tweets:

  1. when initialized, load tweet count aggregated by date.
  2. when selecting a time range, request for the exact tweet id and location with in the time range.
  3. select tweets based on map range
  4. frontend buffer to cache tweets for duplicate or overlap selection
@Yicong-Huang
Copy link
Contributor Author

reopened as more fix are ongoing.

@Yicong-Huang Yicong-Huang reopened this Oct 14, 2019
@Yicong-Huang Yicong-Huang assigned yuanf9 and unassigned XinyueHan7 Oct 17, 2019
@Yicong-Huang
Copy link
Contributor Author

how is this issue?

@yuanf9
Copy link
Contributor

yuanf9 commented Oct 25, 2019 via email

@Yicong-Huang
Copy link
Contributor Author

no please focus on fixing the current demo. let @XinyueHan7 and @AC-Unicorn deal with the new frontend.

we need the current frontend to be working by next Thursday, as we need a new demo. Right now the current frontend is not so functional.

@yuanf9
Copy link
Contributor

yuanf9 commented Oct 25, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants