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

why does eval report out of memory while n_scale is set the same in train and eval? #184

Open
xu19971109 opened this issue Jul 18, 2022 · 0 comments
Open

why does eval report out of memory while n_scale is set the same in train and eval? #184

xu19971109 opened this issue Jul 18, 2022 · 0 comments

Comments

@xu19971109
Copy link

N_scale is set the same in train and eval, batch 2 or batch 4 can be used in training, but eval will report out of memory error after batch 2 or batch 4 is run.
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
@xu19971109