Skip to content
This repository has been archived by the owner on Nov 20, 2022. It is now read-only.

Projections in pipeline are lazily evaluated. #8

Closed
Akii opened this issue Nov 4, 2018 · 3 comments
Closed

Projections in pipeline are lazily evaluated. #8

Akii opened this issue Nov 4, 2018 · 3 comments
Assignees
@Akii
Labels
bug
Projects
Iteration 3

Comments

@Akii
Copy link
Owner

Akii commented Nov 4, 2018

This has following implications:

  • initial request takes 12 seconds
  • subsequent requests take 200 ms
  • requests after some events take 2 seconds

Needs to be strictly evaluated in order to be fast.
@Akii Akii added the bug label Nov 4, 2018
@Akii Akii added this to To do in Iteration 3 Nov 4, 2018
@Akii Akii moved this from To do to In progress in Iteration 3 Nov 5, 2018
@Akii Akii moved this from In progress to To do in Iteration 3 Nov 5, 2018
@Akii Akii moved this from To do to In progress in Iteration 3 Nov 12, 2018
@Akii
Copy link
Owner Author

Akii commented Nov 12, 2018

Basic idea: NFData the s**t out of the UI models and keep them in an IORef that refreshes every few seconds (15-ish).

@Akii Akii self-assigned this Nov 12, 2018
@Akii
Copy link
Owner Author

Akii commented Nov 17, 2018

Identified the culprit: It's the disruption projection.

@Akii Akii moved this from In progress to Done in Iteration 3 Nov 17, 2018
@Akii
Copy link
Owner Author

Akii commented Nov 17, 2018

Using the frontend cache and deepseq'ing that data, this is now no longer a problem

@Akii Akii closed this as completed Nov 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Akii Akii

Labels
bug
Projects
No open projects
Iteration 3
  
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Akii