-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
Current performance breakdown of rendering a 512x512 Kottbusser Tor tile:
The actual tile took about 240ms to render (and about 380 CPU milliseconds). |
\o/ |
Note that this isn't node.js-related, and doesn't parallelize anything. |
Wooo, nice to see this moving! |
(e.g. glGetString(GL_EXTENSIONS) doesn't work, you'd have to use glGetStringi(GL_EXTENSIONS, ...);)
|
||
int main(int argc, char *argv[]) { | ||
|
||
std::string style_path; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we were using camel case now?
Looks like headless rendering tests are universally failing on this branch. For comparison, at least some are passing on current master. |
Whoa @jfirebaugh , that looks like what I was seeing from multithreading problems with mixed up contexts at one point. FWIW 57e6bc6 was last known working commit for me. |
Huh, just tested with |
Um, I'm also not seeing a build 1705 (the one that would have generated those failing tests you linked) on Travis @jfirebaugh https://travis-ci.org/mapbox/mapbox-gl-native/builds |
Oops, I guess I followed a link from an old commit. https://travis-ci.org/mapbox/mapbox-gl-native/builds/43837521 Most recent build looks equivalent to master. http://mapbox-gl-testing.s3.amazonaws.com/headless/mapbox/mapbox-gl-native/1719.1/index.html |
Adds a CLI binary that allows rendering static images.
Fixes #623