-
Notifications
You must be signed in to change notification settings - Fork 735
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
GraphQL Playground significant battery drain #653
Comments
Thanks for reporting @heymartinadams ! Which version of the Playground are you using? We had similar issues in previous versions. |
@timsuchanek v1.5.4 |
@heymartinadams do you see this related to #627 or does it occur "always"? |
@schickling it appears to occur always, once a connection to the server has been established. |
@heymartinadams can you record a quick video screencast (I recommend Loom) where you launch the Playground and reproduce the behaviour? |
@schickling where’s access to v1.6.3? Only seeing 1.5.6: https://github.com/graphcool/graphql-playground/releases |
Oh sorry, the versioning scheme is a bit confusing right now. There are two versions:
@heymartinadams do you have the option to try out the same on a different machine as well? |
@schickling not at the moment. Probably in a week from now. |
Mmh. Restarted PG again and this time it appears to be ok! Not sure what happened, @schickling, or why. Closing this unless it comes up again. |
Hmm still sounds suspicious. @heymartinadams (or anyone else), please let us know if this happens again! The more details on how to reproduce this problem you can provide, the better! |
Look at that, @schickling! Saw your notification, so restarted PG and it then did it again. For a minute or so, then it went back to normal CPU usage. During that time of high CPU usage it appears that the schema was in a loading state. Now when I’m restarting and as endpoint simply enter the server name without When I restart and enter the correct endpoint (server url with So that might be the bug that causes the high-CPU use. |
Sometimes, too, I enter the correct server address with |
I updated to the latest npm version and it no longer happens. Looks like it was fixed by |
I'm having the same issues, happening on the latest demo version: https://www.graphqlbin.com/v2/6RQ6TM when i turn polling off in settings it seems to calm down |
Good catch blaiprat! I had no idea that a CSS-specified animation could be so expensive. Apparently as developers we should scrutinize the use of any such animations in our pages. The notion of CSS animations being far less costly than old JS-based hacks seems to be erroneous. edit: Hopefully this pulsation can be reconsidered or at least made optional via user settings. It's definitely not worth it... I hadn't even noticed the darned animation on the smaller screen that window was on. |
Confirm @blaiprat's workaround. After I've disabled schema pooling, my laptop CPU LA gets down from 4 to 1. |
@heymartinadams Alerting you to the significant problem. |
Good to know, @adrianoresende. Will close this issue. 🙌🏼 |
This issue pertains to the following package(s):
Observation
This isn’t an issue, just a helpful observation I wanted to pass onto the community: noticed how running GraphQL Playground in Chrome, even when not using it, quickly depleted my laptop’s battery. But not so with the electron standalone version of the GraphQL Playground.
Energy Impact
GraphQL Playground in Chrome:
Chrome without GraphQL Playground:
GraphQL Playground (standalone):
The text was updated successfully, but these errors were encountered: