Title: Inefficient error-handle for CJK encodings
Type: performance Stage:
Components: Unicode Versions: Python 3.10
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: corona10, ezio.melotti, inada.naoki, malin, serhiy.storchaka, vstinner
Priority: normal Keywords:

Created on 2020-07-18 04:53 by malin, last changed 2020-08-01 05:44 by malin.

File name Uploaded Description Edit
error_handers_fast_paths.txt malin, 2020-07-18 07:37
Messages (8)
msg373871 - (view) Author: Ma Lin (malin) * Date: 2020-07-18 04:53
CJK encode/decode functions only have three error-handler fast-paths:
See the code: [1][2]

If use other built-in error-handlers, need to get the error-handler object, and call it with an Unicode Exception argument. See the code: [3]

But the error-handler object is not cached, it needs to be looked up from a dict every time, which is very inefficient.

Another possible optimization is to write fast-path for common error-handlers, Python has these built-in error-handlers:

    surrogatepass (only for utf-8/utf-16/utf-32 family)

For example, maybe `xmlcharrefreplace` is heavily used in Web application, it can be implemented as a fast-path, so that no need to call the error-handler object every time.
Just like the `xmlcharrefreplace` fast-path in `PyUnicode_EncodeCharmap` [4].

[1] encode function:

[2] decode function:

[3] `call_error_callback` function:

[4] `xmlcharrefreplace` fast-path in `PyUnicode_EncodeCharmap`:
msg373878 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2020-07-18 06:50
I am not even sure it was worth to add fast path for "xmlcharrefreplace". "surrogateescape" and "surrogatepass" are most likely used in performance critical cases. It is also easy to add support of "ignore" and "replace". "strict" raises an exception in any case, and "backslashreplace", "xmlcharrefreplace" and "namereplace" are too complex and used in cases when coding time is not dominant (error reporting, debugging, formatting complex documents).
msg373881 - (view) Author: Ma Lin (malin) * Date: 2020-07-18 07:37
IMO "xmlcharrefreplace" is useful for Web application.

For example, the page's charset is "gbk", then this statement can generate the bytes content easily & safely:

    s.encode('gbk', 'xmlcharrefreplace')

Maybe some HTML-related frameworks use this way to escape characters, such as Sphinx [1].

Attached file `error_handers_fast_paths.txt` summarized all current error-handler fast-paths.

[1] Sphinx use 'xmlcharrefreplace' to escape
msg373885 - (view) Author: Inada Naoki (inada.naoki) * (Python committer) Date: 2020-07-18 08:09
But how many new Python web application use CJK codec instead of UTF-8?
msg373889 - (view) Author: Ma Lin (malin) * Date: 2020-07-18 08:31
> But how many new Python web application use CJK codec instead of UTF-8?

A CJK character usually takes 2-bytes in CJK encodings, but takes 3-bytes in UTF-8.

I tested a Chinese book:
in GBK:     853,025 bytes
in UTF-8: 1,267,523 bytes

For CJK content, UTF-8 is wasteful, maybe CJK encodings will not be eliminated.
msg373890 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2020-07-18 08:39
In the Web application you need first to generate data (this may involve some network requests, IO operations, and some data transformations), then format the page, then encode it, and finally send it to client. I suppose that the encoding part is minor in comparison with others.

Also, as Inada-san noted, UTF-8 is more popular encoding in modern applications. It is also fast, so you may prefer UTF-8 if the performance of encoding is important to you.
msg374616 - (view) Author: Dong-hee Na (corona10) * (Python committer) Date: 2020-07-30 14:48
I am also +1 on Serhiy's opinion.

As I am Korean, (I don't know Japan or China environment)
I know that there still exist old Korean websites that use EUC-KR encoding.
But at least 2010s modern Korea website/application.
Most of the applications are built on UTF-8.
msg374656 - (view) Author: Ma Lin (malin) * Date: 2020-08-01 05:44
At least fix this bug:

    the error-handler object is not cached, it needs to be
    looked up from a dict every time, which is very inefficient.

The code:

I will submit a PR at some point.
Date User Action Args
2020-08-01 05:44:18malinsetmessages: + msg374656
2020-07-30 14:48:43corona10setnosy: + corona10
messages: + msg374616
2020-07-18 08:39:08serhiy.storchakasetmessages: + msg373890
2020-07-18 08:31:13malinsetmessages: + msg373889
2020-07-18 08:09:04inada.naokisetnosy: + inada.naoki
messages: + msg373885
2020-07-18 07:37:10malinsetfiles: + error_handers_fast_paths.txt

messages: + msg373881
2020-07-18 06:50:14serhiy.storchakasetnosy: + serhiy.storchaka
messages: + msg373878
2020-07-18 04:53:39malincreate