# Test results for the current Anslatortray main branch
From Anslatortray 0.3.0 to 0.4.0, the various included programs were consolidated into a single `anslatortray` binary. In addition, this binary recieved a new option `--benchmark-file`, which makes it much easier to evaluate the time it takes to translate a particular file.
On my dated system with dual Intel(R) Xeon(R) E5-2670 v2 CPUs, the `translate()` function can process one word every TODO nanoseconds on average in the default UTF-8 mode, and one word every TODO nanoseconds on average in the ASCII-only mode. The `words_alpha.txt` file from <https://github.com/dwyl/english-words> was fed to the `anslatortray --benchmark-file` set to 10000 iterations.
On my dated system with dual Intel(R) Xeon(R) E5-2670 v2 CPUs, the `translate()` function can process one word every TODO nanoseconds on average in the default UTF-8 mode, and one word every TODO nanoseconds on average in the ASCII-only mode. The `words_alpha.txt` file from <https://github.com/dwyl/english-words> was fed to the `anslatortray --benchmark-file` set to 1000 iterations, and then the averages produced were divided by 370105 (the number of words in the file).
TODO
Although `cargo bench --features nightly-features` benchmarks are still supported, I am no longer including them
Although `cargo bench --features nightly-features` benchmarks are still supported, I am no longer including them on this page as what they actually compute changes frequently. They're mostly intended for quick regression testing during development.
