Try Fix Mistral Compile on T4
Author: zhenglongjiepheonix
Pull request: yes
Labels: name: Compilation

name: run-slow

# What does this PR do?

<!--
Congratulations! You've made it this far! You're not quite done yet though.

Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution.

Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change.

Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost.
-->

<!-- Remove if not applicable -->

Fixes # (issue)


## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [ ] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

<!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @

 If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**.
 Please tag fewer than 3 people.

Models:

- text models: @ArthurZucker and @younesbelkada
- vision models: @amyeroberts
- speech models: @sanchit-gandhi
- graph models: @clefourrier

Library:

- flax: @sanchit-gandhi
- generate: @zucchini-nlp (visual-language models) or @gante (all others)
- pipelines: @Narsil
- tensorflow: @gante and @Rocketknight1
- tokenizers: @ArthurZucker
- trainer: @muellerzr and @SunMarc

Integrations:

- deepspeed: HF Trainer/Accelerate: @muellerzr
- ray/raytune: @richardliaw, @amogkam
- Big Model Inference: @SunMarc
- quantization (bitsandbytes, autogpt): @SunMarc and @younesbelkada

Documentation: @stevhliu and @MKhalusova

HF projects:

- accelerate: [different repo](https://github.com/huggingface/accelerate)
- datasets: [different repo](https://github.com/huggingface/datasets)
- diffusers: [different repo](https://github.com/huggingface/diffusers)
- rust tokenizers: [different repo](https://github.com/huggingface/tokenizers)

Maintained examples (not research project or legacy):

- Flax: @sanchit-gandhi
- PyTorch: See Models above and tag the person corresponding to the modality of the example.
- TensorFlow: @Rocketknight1

 -->


Comments:
The docs for this PR live [here](https://moon-ci-docs.huggingface.co/docs/transformers/pr_31318). All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

cc @ydshieh 

Will check, but probably it's not ready yet.

> Will check, but probably it's not ready yet.

Yes, I think it's related to dynamo needing more memory when tuning parameters for kernels, and I think gpu memory might not release in time between tests, in colab T4 env sometimes it passes sometimes it fails, still trying to make it work under little memory budget on T4

A few things to share from my experience:

- run that single test to see if it ever fails
  - in this case, we don't have much choice. We could could try:
    - reduce the input length and/or the generation length 
    - Try `run_test_in_subprocess`
    - Try the hack fix I added in https://github.com/huggingface/transformers/pull/31263/files (the `0,1,2,3` stuff)  

But feel free to try anything you can think of. Happy to know if there are new ways!

> A few things to share from my experience:
> 
> * run that single test to see if it ever fails
>   
>   * in this case, we don't have much choice. We could could try:
>     
>     * reduce the input length and/or the generation length
>     * Try `run_test_in_subprocess`
>     * Try the hack fix I added in https://github.com/huggingface/transformers/pull/31263/files (the `0,1,2,3` stuff)
> 
> But feel free to try anything you can think of. Happy to know if there are new ways!

Yes, the single test alone can fail, and it would require about 14GB out of 15GB available total GPU memory on T4 to load the model and do inference even if we don't do compile, and reduce length won't help because the kv cache only takes a small part of the used memory

OK then. It's fine for me if we only run this on A10. We have a CI workflow will run it on A10

.github/workflows/push-important-models.yml

(But feel free if you still want to try anything when you have time)

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.

Please note that issues that do not follow the [contributing guidelines](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md) are likely to be ignored.