rust-numpy VS tokenizers

On the contrary, it can use and interface with numpy quite easily: https://github.com/PyO3/rust-numpy

Once I figured out the right tools, it was easy. Its just "maturin new". It automatically converts python floats and strings. Numpy arrays come through as a special Pyarray type, that you need to unwrap, but that's just one builtin function. Using pyo3, maturin and numpy, https://github.com/PyO3/rust-numpy it's fairly easy.

If I'm understanding this documentation correctly then you may be able to pass the numpy array directly with func(df['col'].to_numpy) which may save some conversion.

Otherwise, though, Rust is an excellent choice. The many advantages of Rust (great package manager, memory safety, modern language features, ...) are already well documented so I won't repeat them here. Specifically for writing Python libraries, check out PyO3, maturin, and rust-numpy, which allow for seamless integration with the Python scientific computing ecosystem. Dockerizing/packaging is a non-issue, with the aforementioned libraries you can easily publish Rust libraries as pip packages or compile them from source as part of your docker build. We have several successful production deployments of Rust code at OpenAI, and I have personally found it to be a joy to work with.

Integration with numpy uses the rust-numpy crate: Example of method that accepts numpy arrays as arguments Example of a method that returns a numpy array to Python (this performs a copy, there ought to be a way to avoid it but the current implementation has been plenty fast for my use case so far)

This example maybe helpful.

Given that it's via pyO3, you could even pass the numpy arrays using https://github.com/PyO3/rust-numpy and get ndarrays at the other side.

Same no copy, slightly more user friendly approach.

Further criticism of the actual approach - even if we didn't do zero copy, there's no preallocation for the vector despite the size being known upfront, and nested vectors are very slow by default.

So you could speed up the entire thing by passing it to ndarray, and then running a single call to sum over the 2D array you'd find at the other end. (https://docs.rs/ndarray/0.15.1/ndarray/struct.ArrayBase.html...)

I believe converting between pandas Series (e.g. columns) and numpy ndarrays can be pretty cheap, right? Once they're in that format, you can use rust to work directly on the numpy memory buffer with rust-numpy. Otherwise, feather is a format designed for IPC of columnar data; pyarrow is in pandas (might be an optional dependency) and may be pretty quick for that, and rust has an arrow implementation too.

https://github.com/PyO3/rust-numpy

Hugging Face seems to like Rust. They also wrote Tokenizers in Rust.

Your intuition is right. There are two ways (in increasing order of result performance) : 1. You can simply extend vocab file of the tokenizer and test the predictions 2. You can extend the vocab file and re-train your model on custom data which has these new tokens. Check the following issue on GitHub : https://github.com/huggingface/tokenizers/issues/247

SentencePiece -> implementation of some algorithms (there are several others, https://github.com/microsoft/BlingFire https://github.com/glample/fastBPE https://github.com/huggingface/tokenizers )

In sum I would like the idea to go with Rust as I more or less got to rewrite the whole thing anyway, but I am a bit skeptical if I will be able to interface with everything that might come up at some point. Or probably end up in a wrapper hell if I got to use more C++ libraries. On the other hand there are definitely a few Rust projects out there that might come in handy (for example https://github.com/huggingface/tokenizers). And the build process is pretty awful right now (CMake it is but with lots of hacks).

A full machine learning pipeline usually comprises far more than just the model, and this is the area where Rust may shine (the recent work by HuggingFace and their https://github.com/huggingface/tokenizers library is a good example)

As for other tokenizers, you can take a look at - Huggingface tokenizers library: https://github.com/huggingface/tokenizers - NLTK tokenize: https://www.nltk.org/api/nltk.tokenize.html - Polygot: https://pypi.org/project/polyglot/

Huggingface Tokenizers (https://github.com/huggingface/tokenizers), which are now used by default in their Transformers Python library, use pyO3 and became popular due to the pitch that it encoded text an order of magnitude faster with zero config changes.

It lives up to that claim. (I had issues with return object typing when going between Python/Rust at first but those are more consistent now)

huggingface/tokenizers (Rust): 💥Fast State-of-the-Art Tokenizers optimized for Research and Production