4 ms·
jawdropped Are you using PhantomJS to render the page? (that "Notice: last satellite flyover was [x] minutes ago") I'm guessing you queued the job via beansta
by edwinnathaniel 14y ago
jawdropped
Are you using PhantomJS to render the page? (that "Notice: last satellite flyover was [x] minutes ago")
I'm guessing you queued the job via beanstalkd and call phantomjs renderBase64 against your URL?
It's nice to see more people using PhantomJS these days (I'm using it myself in my current work)
- stevejohnson 14y agoYou are a very good guesser. Today's activity has given us a few ideas about how to make those "flyovers" more frequent.
- edwinnathaniel 14y agoI hope these few nuggets about PhantomJS can help your app: - Use JPG and not PNG (for renderBase64), we tested it and JPG gives a much more better performance, but then again it depends on how crisp you want your output - (You may already done this either using PhantomJS or using image manipulation) Don't forget you can also scale the image using page.zoomFactor :) - (Not sure how useful this one is for your case) You can clip the viewport too in PhantomJS - PhantomJS seems to use a lot of memory (main page of twitter.com may resulted in at least 45MB of memory). - CasperJS is probably the best wrapper of PhantomJS out there for now if you ever need to do something more complicated