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

[question] desktop PC with non ECC RAM and lightGBM #6571

Open
luigimacedonia opened this issue Jul 26, 2024 · 0 comments
Open

[question] desktop PC with non ECC RAM and lightGBM #6571

luigimacedonia opened this issue Jul 26, 2024 · 0 comments
Labels

Comments

@luigimacedonia
Copy link

I am (starting to be) aware of the risks of using non ECC memory. I read that basically you cannot trust anything that was generated by a computer without error checking memory. I also read that DDR5 performs a basic check inside the chip that guarantees that it will be correct while the data is still inside the chip (no warranties after it is transferred to the CPU)

Now I would like to know the scope of corruption I could get while training and predicting for instance a classifier with hundreds of features and several millions of samples in the following scenarios:

  1. DDR4, 'device_type': 'cpu'
  2. DDR4, 'device_type': 'gpu'
  3. DDR5, 'device_type': 'cpu'
  4. DDR5, 'device_type': 'gpu'

As a hobbyist, I am using a desktop PC. I am thinking 2 options: to move from Intel to AMD Ryzen Series 9000 to -at least- get unbuffered ECC support or go full for a Threadripper, which is a cutie but it is 3X more expensive. That makes me wonder:

  1. does a faster processor improves the performance of training a model while using 'device_type': 'gpu' ?

thanks

(I didn't know where to post this question. It was deleted from stackoverflow because it doesn't contain a code question. please let me know if it is making noise here and should be deleted)

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

No branches or pull requests

2 participants