Use shallow copy in core/serialize/serializer.py to improve efficiency - #1114
Open
adlantz wants to merge 2 commits into
Open
Use shallow copy in core/serialize/serializer.py to improve efficiency#1114adlantz wants to merge 2 commits into
adlantz wants to merge 2 commits into
Conversation
adlantz
marked this pull request as ready for review
September 4, 2026 18:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #336 asks for improvements to the
tfq.convert_to_tensor speedfunction. The majorirty of the run time occurs in the cirq serialization logic:Inspecting
serialize_circuitI noticed a quick win would be to not do a full deep copy of the input circuit, instead create a shallow copy withcircuit = circuit_inp.copy(). The risk with this is that we may modify the input circuit (change in behavior). We can get away with this because moments are replaces rather than edited in place by the serializer, i.eThat being said, in the controlled operations demotion loop, we reference and mutate
op.sub_operationwhich points to an attribute on the input circuit. Therefore, we make a copy there of each sub operation.Overall the speedup is significant:
The downside is less peace of mind that the input circuit is not mutated, and any changes here in the future need to keep that in mind.
I added a test to ensure serialization does not mutate the input circuit.