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.

Sign up for GitHub

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

Jump to bottom

Bad performance when using operator API to send commands #63

Closed
markvandenbergh opened this issue Aug 4, 2017 · 1 comment
Closed

Bad performance when using operator API to send commands #63

markvandenbergh opened this issue Aug 4, 2017 · 1 comment

Comments

@markvandenbergh
Copy link
Contributor

For some chargers the operator API response time is very high (> 30 seconds). Messages coming from the charger are processed in a normal timeframe.

This is caused by large collections of (for example) opening times on the charger entity in the operator API. The collections were eagerly fetched while this is in many cases not needed.
@markvandenbergh
Copy link
Contributor Author

Fixed with 9220958

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@markvandenbergh