Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate to orjson as the default json serializer #7

Open
sidmitra opened this issue Apr 7, 2022 · 0 comments
Open

Migrate to orjson as the default json serializer #7

sidmitra opened this issue Apr 7, 2022 · 0 comments

Comments

@sidmitra
Copy link
Contributor

sidmitra commented Apr 7, 2022 •
edited
Loading

We should move to orjson later just like our backend DRF serializer. It can be an order of magintude faster, especially useful here where we want to minimize CPU bound stuff and do asyncio/gevent for IO bound stuff.

Long term: see how close are we to adopting protobuf, avro etc. Do we get schema sharing, migration benefits there?
@sidmitra sidmitra changed the title Migrate to orjson as the json serializer Migrate to orjson as the default json serializer Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sidmitra