Skip to content

feat: Use Cirq's Gzip serialization - #1443

Open
drwillcharles wants to merge 2 commits into
mainfrom
wc/cirq-gzip-circuit-serialization
Open

feat: Use Cirq's Gzip serialization#1443
drwillcharles wants to merge 2 commits into
mainfrom
wc/cirq-gzip-circuit-serialization

Conversation

@drwillcharles

Copy link
Copy Markdown
Contributor

We recently had some very large circuits that caused Superstaq server to run out of memory and crash. I think this change would help significantly to reduce the amount of data stored in the database.

Testing a very large circuit (with depth 36) this change reduces the amount of space used by a factor of 50.

We will also need to do some kind of integration test with the Superstaq server to ensure this doesn't break any tests.

@CLAassistant

CLAassistant commented Sep 7, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@drwillcharles

drwillcharles commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Another possible solution instead of implementing cirq.to_json_gzip():

  • Use gzip on the complete HTTP request bodies (Content-Encoding: gzip). This would require support from the server-side to unzip the payload but would make things simpler.
  • On the server-side: change the circuit database fields to GZIP and migrate existing data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants