Skip to content

[Feature]: miniCOIL: no way to control input sequence length (and VRAM usage) natively #544

Open

Description

@elia-morrison

What feature would you like to request?

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?

No response

Activity

  1. 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
  2. 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
  3. hemantgarg26 commented on Jul 23, 2025

    @hemantgarg26

    Is this issue relevant, can I take it up ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions