Skip to content

Cache chip specs #28

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.

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

Open
notmgsk opened this issue Aug 16, 2023 · 0 comments
Open

Cache chip specs #28

notmgsk opened this issue Aug 16, 2023 · 0 comments

Comments

@notmgsk
Copy link
Contributor

notmgsk commented Aug 16, 2023

Deserializing a chip spec from JSON is slow in quilc (on the order of 1s for an Aspen-M-3 chip). In quilc, we got around that by adding a chip cache, so that only the first use of the chip was slow. We ought to include the same to alleviate that slow deserialization.

Alternatively, we could:

  • make use of the caching already in quilc
  • improve performance in quilc

The former is reasonable, but would be gated by review from quil-lang; if we instead implement it here, we can move quicker. The latter alternative is not a sure-thing and would take a good amount of effort. So I think managing the cache ourselves is the best option.

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

No branches or pull requests

1 participant