You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: miniCOIL: no way to control input sequence length (and VRAM usage) natively #544
As I understand it, the interface of the miniCOIL model does not allow users to control the length of tokens passed to the base transformer model. As miniCOIL uses an 8k context model as a backbone, users will be suddenly running out of GPU memory when processing large texts.
Adding a max_sequence_length or similar parameter would be nice.
An easy option to avoid OOMs is to truncate the input string, but it is wrong on many levels.
Is there any additional information you would like to provide?
changed the title [-][Feature]: miniCOIL: no way to native control input sequence length (and VRAM usage)[/-][+][Feature]: miniCOIL: no way to control input sequence length natively (and VRAM usage)[/+]on Jul 16, 2025
changed the title [-][Feature]: miniCOIL: no way to control input sequence length natively (and VRAM usage)[/-][+][Feature]: miniCOIL: no way to control input sequence length (and VRAM usage) natively[/+]on Jul 16, 2025
Activity
[-][Feature]: miniCOIL: no way to native control input sequence length (and VRAM usage)[/-][+][Feature]: miniCOIL: no way to control input sequence length natively (and VRAM usage)[/+][-][Feature]: miniCOIL: no way to control input sequence length natively (and VRAM usage)[/-][+][Feature]: miniCOIL: no way to control input sequence length (and VRAM usage) natively[/+]hemantgarg26 commentedon Jul 23, 2025
Is this issue relevant, can I take it up ?