rigetti / rigetti/libquil-sys

Benchmarking: what is performance like when compared to conventional usage of the servers?

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1
Forks
0
Avg merge
18m
Merged PRs (30d)
1

Description

We should understand any potential performance differences between conventional usage of the quilc and qvm servers and this in-process library. We should be sure to test both single and multi-threaded workloads.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by identifying how the in-process library exposes quilc and qvm functionality, then determine how conventional server usage can be measured alongside it for single- and multi-threaded workloads. Done means having comparable performance results for both workload types.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.