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

Add discussion about program execution statistics in MinCutKarger #2

Open
jkomyno opened this issue Jun 8, 2020 · 0 comments
Open
Labels
documentation Improvements or additions to documentation

Comments

@jkomyno
Copy link
Owner

jkomyno commented Jun 8, 2020

In MinCutKarger, we have the following statistics:

  • the longest discovery time takes is seconds, corresponding to the graph input_random_38_200.txt;
  • the longest full_contraction execution takes 9 milliseconds, corresponding to the graph input_random_40_200.txt;
  • the average running time is 176 seconds;
  • the average discovery_time / program_time ratio is 0,142401742 when no timeout is used;
  • the maximum discovery_time / program_time ratio is 0,897164825 when no timeout is used, corresponding to the graph input_random_1_6.txt.
  • the second-highest discovery_time / program_time ratio is 0.833009709 when no timeout is used, corresponding to the graph input_random_4_6.txt
@jkomyno jkomyno added the documentation Improvements or additions to documentation label Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant