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.

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

For a release build, performance could be better #7

Open
tannerhelland opened this issue Jan 7, 2019 · 0 comments
Open

For a release build, performance could be better #7

tannerhelland opened this issue Jan 7, 2019 · 0 comments

Comments

@tannerhelland
Copy link

While performance may not be relevant to all users, I'm a little curious why perf of this build is poor relative to other builds.

For reference I have run small comparisons on this build vs a fresh build using VS2017 + v141_xp toolchain built with /O2 (similar to this one ), and also Olaf's cairo/sqlite mashup from http://www.vbrichclient.com/#/en/Downloads.htm (which can be used as a "drop-in replacement" for VBcairo.dll).

Testing something simple like rendering a large radial gradient (8 mp) yields times roughly on the range of 800 ms for this build, 600 ms for Olaf's build, and 400 ms for a default /O2 build. Linear gradients show a similar perf spread.

These timings seem particularly odd since Olaf's cairo is based off a very old build (1.9.4 as reported by the dll) and I would expect at least some pixman improvements since then.

Given that an /O2 build adds barely 200 kb to the final dll, would it be worthwhile to revisit current optimization settings?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant