Skip to content
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

feat(libp2p): Optional async std libp2p & profiling profile #1454

Merged
merged 8 commits into from
Feb 13, 2023

Conversation

gurinderu
Copy link
Contributor

@gurinderu gurinderu commented Feb 10, 2023

No description provided.

@gurinderu gurinderu force-pushed the optional-async-std-libp2p branch 4 times, most recently from c04b27a to 7b5e71c Compare February 10, 2023 12:40
@gurinderu gurinderu changed the title Optional async std libp2p сhore: Optional async std libp2p Feb 10, 2023
@gurinderu gurinderu changed the title сhore: Optional async std libp2p feat: Optional async std libp2p Feb 10, 2023
@gurinderu gurinderu changed the title feat: Optional async std libp2p feat: Optional async std libp2p & debug profile Feb 13, 2023
@gurinderu gurinderu marked this pull request as ready for review February 13, 2023 09:14
@gurinderu gurinderu requested a review from folex February 13, 2023 09:20
@@ -59,11 +59,11 @@ jobs:
publish: false

- name: Run cargo build
run: cargo build --release -p particle-node
run: cargo build --profile release-with-debug -p particle-node
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we want that for every snapshot. WDYT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For dev purposes, it is extremely useful. You can debug and profile these images.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this approach, we loose non-dev snapshots for the branch.

These snapshots are used in three ways:

  1. in e2e tests, where these snapshots must be fast
  2. to deploy temporary fixes to our environments, even to kras, and it must be fast there
  3. profiling - pretty rare thing

To me, it seems that profile-able images are better to be ran on request. Maybe manually changing profile to profiling (aka release-with-debug) in CI scripts is a good-enough approach.

If we choose that path, then I'd keep profile in Cargo.toml, but rename it to profiling.

@nahsi nahsi added the profiling build with debug profiling label Feb 13, 2023
@folex folex changed the title feat: Optional async std libp2p & debug profile feat(libp2p): Optional async std libp2p & debug profile Feb 13, 2023
@gurinderu gurinderu enabled auto-merge (squash) February 13, 2023 15:14
@gurinderu gurinderu changed the title feat(libp2p): Optional async std libp2p & debug profile feat(libp2p): Optional async std libp2p & profiling profile Feb 13, 2023
@gurinderu gurinderu merged commit 1aab9f7 into master Feb 13, 2023
@gurinderu gurinderu deleted the optional-async-std-libp2p branch February 13, 2023 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
profiling build with debug profiling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants