Skip to content
This repository has been archived by the owner on Jan 8, 2025. It is now read-only.

epic: diff-profiling between cairo zero and cairo for Kakarot Core EVM #812

Open
3 tasks
Eikix opened this issue Aug 7, 2024 · 1 comment
Open
3 tasks
Assignees
Labels
enhancement New feature or request epic Macro-task - Usually a collection of sub-issues

Comments

@Eikix
Copy link
Member

Eikix commented Aug 7, 2024

In an effort to highlight parts that could be optimized by the compiler, produce several benchmarks of core components and functions of the Kakarot implementation, and compare them to their CairoZero counterpart.

Profiling can be done using the cairo-profiler

Data Structures

  • Profile the Stack
  • Profile the Memory

Utils

  • Profile conversion from and to bytes

Needs more scoping.

@Eikix Eikix added the enhancement New feature or request label Aug 7, 2024
@github-project-automation github-project-automation bot moved this to 🆕 Backlog in Kakarot on Starknet Aug 7, 2024
@Eikix Eikix moved this from 🆕 Backlog to 🔖 Ready in Kakarot on Starknet Aug 8, 2024
@Eikix
Copy link
Member Author

Eikix commented Aug 8, 2024

Problem reported by @enitrat:

  • Packages moved to sn-foundry can be profiled easily
  • Cannot move tests to sn-foundry without rewriting effort

Solution:

  • Profile when it is easy with sn-foundry to assert if the profiling is good -> assert whether we want sn-foundry for profiling or custom dev effort
  • Later, move tests

@Eikix Eikix moved this from 🔖 Ready to 🏗 In progress in Kakarot on Starknet Aug 8, 2024
@ClementWalter ClementWalter added the epic Macro-task - Usually a collection of sub-issues label Oct 21, 2024
@ClementWalter ClementWalter moved this from 🏗 In progress to 🆕 Backlog in Kakarot on Starknet Oct 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request epic Macro-task - Usually a collection of sub-issues
Projects
No open projects
Status: 🆕 Backlog
Development

No branches or pull requests

3 participants