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

Investigate memory usage improvements in StringEncoder and TextEncoder #1246

Open

GaelVaroquaux opened this issue Feb 25, 2025 · 1 comment

Labels

Member

GaelVaroquaux commented Feb 25, 2025

I just blew up the memory of my computer using the StringEncoder and TextEncoder.

I have not look at their code, but I was wondering if we could check that they use float32 internal representations, and if not ensure this.

GaelVaroquaux added the enhancement label

Member Author

GaelVaroquaux commented Feb 26, 2025

Tackled by #1248 for the StringEncoder

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