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

Time controls: heatmap #2

Open
3 tasks done
sbrl opened this issue Feb 1, 2019 · 3 comments
Open
3 tasks done

Time controls: heatmap #2

sbrl opened this issue Feb 1, 2019 · 3 comments
Labels
complexity: high It's wildly complicated. enhancement New feature or request

Comments

@sbrl
Copy link
Collaborator

sbrl commented Feb 1, 2019

The heatmap also needs a time control on it, but I suspect it'll end working very differently to the device graph.

  • Re-investigate leaflet-timedimension
  • Get bounds from PHP API
  • Fetch new heatmap data and display it based on leaflet-timedimension event
@sbrl sbrl added the enhancement New feature or request label Feb 1, 2019
@sbrl
Copy link
Collaborator Author

sbrl commented Apr 23, 2019

We've made progress here & rolled out some controls, but we've got some performance issues to deal with. We should track those down & maybe alter the UI a bit to make it easier to select a time (it's only going to get harder as we generate more data lol :P) before closing this issue.

@sbrl
Copy link
Collaborator Author

sbrl commented May 14, 2019

With respect to the performance issues, it's possible that the Apache server that's hosting the web interface isn't using FastCGI, instead opting for the (much) slower CGI. We'll have to investigate.

  • Check that the server is using FastCGI
  • Investigate possibility of using PHP-FPM
  • Add server-side caching layer for output of appropriate actions
  • Consider using a separate server(?) with Nginx if we need more speed?

To be honest though, we really need to fix #30 first though. It's a seriously nasty bug that may result in us moving to a different plugin :-/

@sbrl
Copy link
Collaborator Author

sbrl commented Jun 23, 2019

Bother it all. With the new heatmap implementation, we're back to square 1 with this issue.

Thankfully, the performance issues have been somewhat alleviated by the squashing of a bunch of nasty datetime format warnings. We'll see how much of a difference this'll make to a fancy animation time controls system when we get around to implementing this again.

We'll probably have to do something about the leaflet-timedimension default UI though, because its; not exactly suitable for our usage. Maybe a calendar & clock or something might work, with some arrows to jump forwards & backwards by set amounts (6 minutes, 1 hour, 1 day, custom, etc.?) might work?

Thought it needed.

@sbrl sbrl added the complexity: high It's wildly complicated. label Jun 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: high It's wildly complicated. enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant