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

          Activity

          Bartosz Tarnawski made changes -
          Field Original Value New Value
          Link This issue is related to SIO-1401 [ SIO-1401 ]
          Bartosz Tarnawski made changes -
          Description 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.
          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.
          Bartosz Tarnawski made changes -
          Link This issue is related to SIO-1253 [ SIO-1253 ]
          Michał Łazowik made changes -
          Assignee Michał Łazowik [ mlazowik ]
          Szymon Acedański made changes -
          TAG Developer Michał Łazowik [ mlazowik ]
          TAG Reviewer Sebastian Jaszczur [ jaszczur ]
          Michał Łazowik made changes -
          Status New [ 10000 ] Open [ 1 ]
          Michał Łazowik made changes -
          Assignee Michał Łazowik [ mlazowik ]
          Michał Łazowik made changes -
          TAG Developer Michał Łazowik [ mlazowik ]
          TAG Reviewer Sebastian Jaszczur [ jaszczur ]
          Adam Paszke made changes -
          Affects Version/s TAG 2015/16 Sprint 2 [ 12401 ]
          Affects Version/s Current Version [ 11000 ]
          Adam Paszke made changes -
          Labels T2
          Adam Paszke made changes -
          Fix Version/s TAG 2015/16 Sprint 2 [ 12401 ]
          Adam Paszke made changes -
          Fix Version/s TAG 2015/16 Sprint 2 [ 12401 ]
          Stanisław Barzowski made changes -
          Fix Version/s TAG 2015/16 Sprint 3 [ 12402 ]
          Affects Version/s Current Version [ 11000 ]
          Affects Version/s TAG 2015/16 Sprint 2 [ 12401 ]
          Description 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.
          (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.
          Adam Paszke made changes -
          Link This issue relates to SIO-1766 [ SIO-1766 ]
          Adam Paszke made changes -
          Assignee Adam Paszke [ apaszke ]
          Adam Paszke made changes -
          TAG Reviewer Stanisław Barzowski [ sbarzowski ]
          Adam Paszke made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Assignee Adam Paszke [ apaszke ] Szymon Acedański [ accek ]
          Resolution Fixed [ 1 ]
          Adam Paszke made changes -
          TAG Developer Adam Paszke [ apaszke ]
          Szymon Acedański made changes -
          Fix Version/s TAG 2015/16 [ 12500 ]
          Fix Version/s TAG 2015/16 Sprint 3 [ 12402 ]
          Bartosz Tarnawski made changes -
          Link This issue relates to SIO-1896 [ SIO-1896 ]
          Szymon Acedański made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            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: