You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to have a profiler that helps quickly estimate resource costs each line of a Noir program contributes, hence more easily optimizing proving performance of Noir programs.
The MVP user workflow should look something like:
Developer runs nargo info --verbose
Nargo prints # of ACIR opcodes associated with each line, e.g.
fn main(x : Field) {
foo(x) // -> 100 opcodes
bar(x) // -> 200 opcodes
let y = x + x; // -> 1 opcode
}
The content you are editing has changed. Please copy your edits and refresh the page.
Not to be achieved with this Issue. More as extra context and for discussions where necessary.
The full vision could be:
VS Code extension always display the # of ACIR opcodes next to each line of Noir code
When the developer hovers over the #, it additionally displays:
a. # of backend constraints
b. Estimated proving time
c. Estimated proving memory needs
Assigning P-MEDIUM as this greatly helps the Private Kernel Circuit rewrite project and Noir gate golfers out there, but not necessarily blocking any works.
MVP Scope
It would be great to have a profiler that helps quickly estimate resource costs each line of a Noir program contributes, hence more easily optimizing proving performance of Noir programs.
The MVP user workflow should look something like:
nargo info --verbose
Tasks
nargo info
output as vscode code lens #2942function -> lines -> opcodes
mapping #3435nargo::ops::compile
andnargo_cli:clie:compile_cmd
#3503Additional context - full vision
Not to be achieved with this Issue. More as extra context and for discussions where necessary.
The full vision could be:
a. # of backend constraints
b. Estimated proving time
c. Estimated proving memory needs
Based on:
The text was updated successfully, but these errors were encountered: