1. 05 Oct, 2017 2 commits
  2. 22 Sep, 2017 1 commit
  3. 11 Jul, 2017 1 commit
  4. 10 Jul, 2017 1 commit
  5. 07 Jul, 2017 1 commit
  6. 06 Jul, 2017 1 commit
  7. 12 Jun, 2017 1 commit
  8. 05 Jun, 2017 4 commits
  9. 27 Apr, 2017 1 commit
  10. 07 Apr, 2017 1 commit
  11. 06 Apr, 2017 1 commit
  12. 09 Mar, 2017 1 commit
  13. 23 Feb, 2017 1 commit
    • Test Speedup: Isolate Modulestore Signals · 2051c909
      There are a number of Django Signals that are on the modulestore's
      SignalHandler class, such as SignalHandler.course_published. These
      signals can trigger very expensive processes to occur, such as course
      overview or block structures generation. Most of the time, the test
      author doesn't care about these side-effects.
      
      This commit does a few things:
      
      * Converts the signals on SignalHandler to be instances of a new
        SwitchedSignal class, that allows signal sending to be disabled.
      
      * Creates a SignalIsolationMixin helper similar in spirit to the
        CacheIsolationMixin, and adds it to the ModuleStoreIsolationMixin
        (and thus to ModuleStoreTestCase and SharedModuleStoreTestCase).
      
      * Converts our various tests to use this new mechanism. In some cases,
        this means adjusting query counts downwards because they no longer
        have to account for publishing listener actions.
      
      Modulestore generated signals are now muted by default during test runs.
      Calls to send() them will result in no-ops. You can choose to enable
      specific signals for a given subclass of ModuleStoreTestCase or
      SharedModuleStoreTestCase by specifying an ENABLED_SIGNALS class
      attribute, like the following example:
      
          from xmodule.modulestore.tests.django_utils import ModuleStoreTestCase
      
          class MyPublishTestCase(ModuleStoreTestCase):
              ENABLED_SIGNALS = ['course_published', 'pre_publish']
      
      You should take great care when disabling signals outside of a
      ModuleStoreTestCase or SharedModuleStoreTestCase, since they can leak
      out into other tests. Be sure to always clean up, and never disable
      signals outside of testing. Because signals are essentially process
      globals, it can have a lot of unpleasant side-effects if we start
      mucking around with them during live requests.
      
      Overall, this change has cut the total test execution time for
      edx-platform by a bit over a third, though we still spend a lot in
      pre-test setup during our test builds.
      
      [PERF-413]
      David Ormsbee committed
  14. 09 Nov, 2016 1 commit
  15. 03 Nov, 2016 1 commit
  16. 18 Oct, 2016 1 commit
    • [TNL-5632] Optimize the single_thread view. · 6704e17a
      Firstly, we're now explicitly instructing the comments service to not
      return thread responses/comments if the request isn't AJAX.  So, if you
      load the URL for a single discussion thread in your browser, this would
      be a non-AJAX call and we'll avoid loading the responses for the entire
      thread behind-the-scenes.  Big win here for large threads.
      
      Next, we removed a redundant "get threads" call which was also happening
      behind-the-scenes.  This call was redundant as the front-end JS also
      grabs the thread list when a topic is chosen, so we were making an
      extranenous call for no benefit.  Poof, gone!
      
      Finally, we added some caching of database queries that are required to
      drive a lot of the permissions/cohorts machinery around discussion.
      This will have a minimal effect but introduced a cleaner way to apply
      general memoization at the per-request level which will let us further
      cache things as we identify them as issues.
      Toby Lawrence committed
  17. 03 Aug, 2016 2 commits
  18. 28 Jun, 2016 1 commit
  19. 15 Jun, 2016 1 commit
  20. 04 May, 2016 1 commit
  21. 02 May, 2016 3 commits
  22. 28 Apr, 2016 1 commit
  23. 12 Apr, 2016 2 commits
  24. 05 Apr, 2016 2 commits
  25. 29 Jan, 2016 1 commit
  26. 10 Nov, 2015 1 commit
  27. 06 Aug, 2015 1 commit
    • Enforce discussions permissions in teams UI. · 2f7fa6fd
      Adds a read-only mode to the discussion module which disables any
      controls for updating the discussion (votes, follows, replies,
      etc). This mode is enabled for users who are not a member of the team,
      and are also not moderators, admins, or community TAs.
      Peter Fogg committed
  28. 04 Aug, 2015 1 commit
  29. 31 Jul, 2015 1 commit
  30. 30 Jul, 2015 1 commit
  31. 13 Jul, 2015 1 commit