-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Improve performance #12
Comments
When I last tried long running phantomjs processes they crashed too often on me, might not be an issue any more though. Then we could spawn n procs and have a work queue for new screenshots. I'm down with trying that but don't have the time right now. |
I could give it a try though I'm not too experienced with sub processes and work queues. How would you communicate between the processes? As far as I know there is no But we could spin up a webserver and communicate via What do you think, should I give it a try using phantomjs-wrapper and open a pull-request? |
And what do you think about just resizing the page? I think this is the way you'd usually test your webpages manually. Why shouldn't review speed up the rendering process by doing it exactly the same way? As I mentioned, it should be opt-out if reloading the page is necessary (but I'd turn it on by default). |
Yeah I think http should be the way to go. And for resizing, SGTM :) |
I'm using review for developing an interactive widget. The widget is designed to run on different screen sizes and different types of data (variable amount of columns). That's why I need to keep an eye on ~15 states.
review is a good support for this task, but unfortunately it takes quite some time to reload 15 screenshots. After digging into the source code I saw that review spawns a child_process for every image. This adds ~2 seconds delay on every image.
I thought about ways how multiple screenshots could be rendered more efficiently:
resize
.What do you think?
The text was updated successfully, but these errors were encountered: