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.

Sign up for GitHub

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

Jump to bottom

Benchmark does not reflect size in browser #46

Closed
gkjohnson opened this issue Dec 20, 2018 · 1 comment
Closed

Benchmark does not reflect size in browser #46

gkjohnson opened this issue Dec 20, 2018 · 1 comment

Comments

@gkjohnson
Copy link
Owner

The benchmark estimates the size of an object based on primitive, array, and dictionary key size calculations, but the javascript engine likely overhead associated with an object.

When computing a bounding box for a TorusKnotBufferGeometry with the arguments TorusKnotBufferGeometry(1, 0.4, 400, 100) the benchmark reports 2476.31 kb (including index buffer) used while the browser reports 6617.08 kb used.

image
@gkjohnson
Copy link
Owner Author

Closing for now -- estimates are good enough

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gkjohnson