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

performance test #632

Open
meejah opened this issue Feb 3, 2022 · 0 comments
Open

performance test #632

meejah opened this issue Feb 3, 2022 · 0 comments
Labels
future Something to consider way later

Comments

@meejah
Copy link
Collaborator

meejah commented Feb 3, 2022

Before tackling any generally "performance" bugs it is desirable to have some idea of whether any changes make things "faster" or "slower" (maybe related "use more resources" or not).

Required:

  • "canonical" test-cases
    • X files with Y data
    • "lots of tiny files"
    • "a few big file" (but same total data as above)
    • "a mix"?
  • times to perform common things
    • wall-clock time to upload some "common case" (e.g. X files with Y data)

Nice to have:

  • CPU times to perform uploads
  • network traffic required to perform uploads
  • (max?) memory usage to perform uploads
  • profiling information (e.g. from vmprof) identifying code-paths to blame for {slow,memory,..}
@meejah meejah added the future Something to consider way later label Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future Something to consider way later
Projects
None yet
Development

No branches or pull requests

1 participant