jango has two i18n-related features when it comes to URL dispatching:
It can translate (portions of) the URL path according to the locale preference of the user
It can prepend a locale code to the URL path according to the locale preference of the user. This is a framework-provided solution to the scenario in the 'seo' section of the benchmark with the difference that the benchmark implements this manually.
In Django the i18n funcionality is controlled by the USE_I18N setting whose default value is True. As the benchmark isn't making use of the above mentioned features, it would be more fair to turn i18n off.