The SIO2 project
  1. The SIO2 project
  2. SIO-1687

Improve ranking caching

        Details

        • Type: Improvement Improvement
        • Status: Closed Closed
        • Priority: Major Major
        • Resolution: Fixed
        • Affects Version/s: Current Version
        • Fix Version/s: TAG 2015/16
        • Component/s: OIOIOI
        • Labels:

          Description

          (Probably a lot of work. Solving it reasonably likely requires drastic changes).

          The current ranking caching strategy is not suitable for contest with many (e.g > 1000) users. It takes around 30s to generate such a ranking and the current RANKING_CACHE_TIMEOUT is set to 30s. Increasing this constant will not solve the problem, as the ranking gets invalidated every time some new solution is judged.

          One of the possible solution could be introducing ranking_cache_timeout in the contest controller, for example 30 mins for contests with many users and 30s for ACM style contests. It is also worth considering to cache rankings separately for contest admins and regular contestants.

          This issue is related to displaying links to "my submissions" in the ranking view. Apparently they get broken when the ranking caching with large timeout is enabled. Maybe this feature should be disabled.

            Issue Links

            is related to

            Improvement - An improvement or enhancement to an existing feature or task. SIO-1253 Make scores in ranking clickable

            • Minor - Minor loss of function, or other problem where easy workaround is present.
            • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

            Improvement - An improvement or enhancement to an existing feature or task. SIO-1401 Add ranking caching

            • Minor - Minor loss of function, or other problem where easy workaround is present.
            • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
            relates to

            Bug - A problem which impairs or prevents the functions of the product. SIO-1896 Invalidate (regenerate) ranking after results publishing or disqualification

            • Major - Major loss of function.
            • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

            Improvement - An improvement or enhancement to an existing feature or task. SIO-1766 Ranking performance measurement

            • Major - Major loss of function.
            • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

              Activity

              Connect your code to JIRA

              Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.

              Git & Mercurial in the cloud

              Collaborate across unlimited private code repositories.
              ConnectFind out more

              Git behind the firewall

              Manage and collaborate on Git repositories behind a firewall.
              ConnectFind out more

              Browse and search code

              Browse, search, and track source code repositories.
              ConnectFind out more
              Find more source code tools on the Atlassian Marketplace

                People

                • Assignee:
                  Szymon Acedański
                  Reporter:
                  Bartosz Tarnawski
                  TAG Developer:
                  Adam Paszke
                  TAG Reviewer:
                  Stanisław Barzowski
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: