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

[GPU] LightGBMError: bin size 3142 cannot run on GPU #6702

Open
crs1910 opened this issue Oct 28, 2024 · 3 comments
Open

[GPU] LightGBMError: bin size 3142 cannot run on GPU #6702

crs1910 opened this issue Oct 28, 2024 · 3 comments
Labels

Comments

@crs1910
Copy link

crs1910 commented Oct 28, 2024

Description

Hi, I encountered an error which has been posted by many people while training a LightGBM model using the GPU: LightGBMError: bin size 3142 cannot run on GPU. This error seems to be related to the max_bin parameter setting. I tried reducing the bin size, but it has not resolved the issue.Just wanted to know if there is any fix for this or how I can train lgb model with categorical features having large number of categories.

Reproducible example


params = {
    'boosting_type': 'gbdt',
    'objective': 'binary',
    'metric': 'binary_logloss',
    'device': 'gpu',
    'max_bin': 200, 
    'num_leaves': 31
}

train_data = lgb.Dataset(X_train, label=y_train)
model = lgb.train(params, train_data)

Environment info

lgb version : 4.5.0
cuda version : 11.8
Python 3.7.13

Thanks in advance.

@jameslamb jameslamb changed the title LightGBMError: bin size 3142 cannot run on GPU [GPU] LightGBMError: bin size 3142 cannot run on GPU Oct 30, 2024
@crs1910
Copy link
Author

crs1910 commented Nov 5, 2024

Hi team, just a gentle reminder.Any update on this ?

@yuhorun
Copy link

yuhorun commented Nov 30, 2024

@crs1910

lgbm version: 4.5.0.99

When using the GPU version of LightGBM, I encountered the error:
LightGBMError: bin size 257 cannot run on GPU.

After checking the issue, I found that a fix for this problem was merged 5 months ago in [#6019]

However, I am still encountering this issue.

Has anyone else encountered this problem? How should I resolve it?

@shiyu1994
Copy link
Collaborator

Thanks for reporting the issue. We will verify to see if it still exists in latest commit. We will report back here soon.

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

4 participants