python / codespeed Goto Github PK

The current state is useless, presents that latest results appeared but does it in a confusing manner.

The frontpage should show a longterm performance trend (geometric mean of all benchmarks) for the main branch for each benchmark worker.

We need to backfill aarch64 results data for daily commit spanning back at least a few months (until May 2023)

Currently the changes page has a number of controls that don't explain what the cryptic fields are. What is "lto-pgo", what is "arm-neoverse"?

After the latest upgrade we are using Django 3.2 and the latest binary of psycopg2.

In order to use Django 4.2, we need to switch to psycopg package as psycopg2 will be deprecated at some point.

After the rebase of speed.python.org on top of master, the Latest Results are not showing anymore on the home page.

If we take a comparison chart like this it looks like the histogram bars are only one pixel wide, which makes them basically impossible to read. Could you tweak the plotting parameters to make them a bit more visible?

Originally requested from @gvanrossum: https://discuss.python.org/t/about-speed-python-org-and-aarch64/22519/21

Both branches for speed.pypy.org and speed.python.org are currently running on Python 2.7 and an out of date Django.

Currently, results don't show which year they are from, which leads to confusion.

The branch https://github.com/python/codespeed/tree/speed.python.org has diverged from https://github.com/python/codespeed/tree/master.

We should rebase speed.python.org changes on top of master branch.

I tried rebasing it and there are a few conflicts to resolve (nothing major though)

We are now tracking AArch64 benchmarks. We need to update the about page to add more details about this machine

Currently you can generate permalinks that lead to a different result. If you don't notice, you will be confused.

In the comparison page there are selectors on executables and benchmarks. In order to be consistent we should have it in the environments list as well.

There is currently a hack to allow continued use of "master" as a branch for new uploaded results. This needs to go away. We've been using "main" for years.

Instead a message "Error while retrieving logs: No logs found" is shown.

This is likely caused by this commit 1bdc67a from @vstinner

get_scm(project) returns always None except when the scm is Mercurial.

Currently, only the main branch is easily traversable in the UI.

The project is using quite old dependencies (e.g.: Django, matplotlib...) We should be updating them.