json.dump(x,f) is much slower than f.write(json.dumps(x))

Bug report

Bug description:

Experimentally I measured a huge performance improvement when I switched my code from

json.dump(x, f, **)

to

f.write(json.dumps(x, **))

Method

I essentially wrote the same contents to different files sequentially and measured the total amount of time taken. The json contents had 1, 300, and 400 entries per level, and 1, 5, and 6 levels of depth. There's quite a level of variance here but this wasn't what I was trying to measure in the first place. I discovered this by chance, so forgive the lack of precision. I also don't have the source code anymore because I wasn't originally planning to report this discovery.

Results

Conclusion

A cursory investigation into the cpython code suggests that the slow part is the sequential writing of the iterencode yield. The chunks are quite small.

CPython versions tested on:

3.10

Operating systems tested on:

macOS

Linked PRs

• gh-130076

まず、リンクされた PR gh-130076 と、iterencode からの逐次書き込みに関係する CPython の JSON コードを確認します。報告されている dump-versus-dumps の時間計測を再現し、その後、出力を変更せずに大きなケースで dump のパフォーマンスが改善されることを検証します。