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

Difference in performance between conda-forge and defaults? #382

Open
1 task
jaimergp opened this issue Nov 15, 2023 · 3 comments
Open
1 task

Difference in performance between conda-forge and defaults? #382

jaimergp opened this issue Nov 15, 2023 · 3 comments
Labels
stale::recovered [bot] recovered after being marked as stale

Comments

@jaimergp
Copy link
Contributor

While running tests for #317 (Linux only), I've noticed on the conda-forge Docker image each attempt takes an average of 15-16s, while on the defaults one it consistently goes down to 5s. I don't know if it's the libsolv version (0.7.26 vs 0.7.24, respectively), or some optimization flags that conda-forge does not set but defaults does.

Leaving this here to investigate in the future, in case it's an obvious win at little cost :)

Ideas to try:

  •  Fetch the duration data from each test run and compare the matched conda-forge&defaults pairs.
@jonashaag
Copy link

We should send fewer packages to libsolv by "presolving", see mamba-org/mamba#2824

Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Dec 12, 2024
@jaimergp
Copy link
Contributor Author

Not stale.

@github-actions github-actions bot added stale::recovered [bot] recovered after being marked as stale and removed stale [bot] marked as stale due to inactivity labels Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale::recovered [bot] recovered after being marked as stale
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants