Skip to content

Book 1: Double vs Float more explanation #752

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
D-K-E opened this issue Oct 6, 2020 · 0 comments
Closed

Book 1: Double vs Float more explanation #752

D-K-E opened this issue Oct 6, 2020 · 0 comments
Assignees
Milestone

Comments

@D-K-E
Copy link

D-K-E commented Oct 6, 2020

It would be nice to have a small overview of pros and cons of using double or float for the end of first book section 3.1. The difference became relevant as I was implementing the second book in cuda.

  • double: more numerical precision
  • double: twice the memory use compared to float
  • float: less numerical precision.
  • float: cuts down the memory use by half compared to double

When I tested the final scene of the second book, I got out of ressources error from cuda, but everything worked fine with float.
Though obvious it is, it might be important to mention that.

@trevordblack trevordblack added this to the Backlog milestone Oct 12, 2020
@hollasch hollasch modified the milestones: Backlog, v4.0.0 Oct 12, 2020
@hollasch hollasch self-assigned this Oct 29, 2020
hollasch added a commit that referenced this issue Nov 3, 2020
@hollasch hollasch closed this as completed Nov 3, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants