Hi @Emanuel,
Thanks for your answer but If you’re right (it is just the first time running the tokenization that results in a bigger time and subsequent calls are faster), this would be a huge problem in production when we need to tokenize one by one the texts (ie, when the user needs it)… and the second question would be then: why the (fast) HF tokenizer acts this way? (what is the tecnical reason behind this "attitude?).