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 on cutoff_len #32

Open
BenoitWang opened this issue Apr 26, 2024 · 1 comment
Open

question on cutoff_len #32

BenoitWang opened this issue Apr 26, 2024 · 1 comment
Labels
question Further information is requested

Comments

@BenoitWang
Copy link

Hi, first thanks for this awesome work. I'm trying to rewrite the training code for ltu-as while I find that the cutoff_len for stage 1 and 2 is 108 which is rather small. There are still many samples that exceed this length and in this case the outputs are cut off. Is this because of a memory issue please?

@YuanGongND YuanGongND added the question Further information is requested label Apr 26, 2024
@YuanGongND
Copy link
Owner

Yes, it is mainly due to computational efficiency consideration.

More specifically, we see a chance to fit a batch size, say 4, to our GPU, and then with this batch size, we find the max seq length, which is something around 108.

The model will see the same data with larger cutoff_len in later stages because we still use these data in later stages.

-Yuan

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

No branches or pull requests

2 participants