1. 27 Mar, 2018 1 commit
  2. 09 Mar, 2018 4 commits
  3. 02 Feb, 2018 1 commit
    • ERP5Type.Core.Folder.recurseCallMethod: Do not change priority for re-call · 24df3ec5
      Increasing priority value (hence making the activity execution priority
      lower) means that all previously-spawned activities will have at least
      started execution before the next batch of activities begins being
      prepared. During that preparation, more activities will end, meaning there
      is then unused processing node time, decreasing processing efficiency.
      
      By making re-call activity have the same priority as spawned activities
      will reduce this delay by making the re-call activity candidate for
      execution at the same time as the latest activity batch, without leading
      to activity queue size increase: older activities within a given priority
      range still get precedence, so any older group will tend to finish before
      more batches get spawned.
      
      Measures on indexing 700k documents with 20 activity nodes:
      - priority + 1: 84k documents indexed in the first 5 minutes,
        47k in the last 5 minutes. Average: 64k/5 minutes
      - priority: 101k documents indexed in the first 5 minutes,
        97k in the last 5 minutes. Average: 99k/5 minutes
      Peak speed (which is the initial speed) is 20% higher.
      As the slowdown rate (likely coming from lower-priority activities piling
      up in the message_queue table) is also much lower in the second case
      (900 fewer documents indexed on each 5 minutes increment instead of 4k),
      the overall average speed improves by 54%.
      Vincent Pelletier committed
  4. 21 Nov, 2017 2 commits
  5. 06 Nov, 2017 2 commits
  6. 20 Oct, 2017 1 commit
  7. 26 Sep, 2017 1 commit
  8. 02 Sep, 2016 1 commit
  9. 15 Jul, 2016 1 commit
  10. 13 Feb, 2016 1 commit
  11. 12 Jan, 2016 1 commit
  12. 24 Nov, 2015 1 commit
  13. 16 Dec, 2014 1 commit
  14. 18 Nov, 2014 2 commits
  15. 06 Nov, 2014 1 commit
  16. 04 Sep, 2014 1 commit
  17. 18 Aug, 2014 1 commit
  18. 01 Apr, 2014 1 commit
  19. 03 Mar, 2014 1 commit
    • reindex: Fix duplicate reindex in Supply and Delivery when more than >100 lines. · 671a83f6
      [Before]:
      
      Where:
      
        in Supply or Delivery(Sale Order, Sale Packing List,..)
      
      When:
      
      ( document.edit(something=some_value)
      
        OR
      
        document.validate(), document.start() something when workflow transition  )
      
      AND
      
        document contains more than 100 sub objects, like 100 lines.
      
      Then:
        /some_module/document/1/recursiveImmediateReindexObject
        /some_module/document/1/reindexObject
        /some_module/document/1/1/recursiveImmediateReindexObject
        .
        .
        /some_module/document/1/100/recursiveImmediateReindexObject
      
      are triggered.
      
      The first big recursiveImmediateReindexObject recursively reindex all the sub
      objects. Thus the following reindex are duplicated.
      
      [After]:
      
      Reindex:
        /some_module/document/1/reindexObject
        /some_module/document/1/1/recursiveImmediateReindexObject
        .
        .
        /some_module/document/1/100/recursiveImmediateReindexObject
      
      The root recursiveImmediateReindexObject is removed.
      
      This has been the expected behavior from the beginning.
      Before was only a side effect by giving empty dict to "if activate_kw == None"
      expression.
      Tatuya Kamada committed
  20. 21 Jun, 2013 1 commit
  21. 26 Apr, 2013 1 commit
  22. 19 Apr, 2013 2 commits
  23. 20 Mar, 2013 1 commit
    • New ERP5 SyncML implementation · 291fafc5
      Complete rewrite of the syncml core engine to make it scallable
      Remaining work :
      - review of conflict management
      - re-implement splitting of big object
      - generic unit test for AsynchronousEngine
      - complete review of default conduit
      - lot of TODO and XXX in the code to check
      Aurel committed
  24. 17 Jan, 2013 1 commit
  25. 17 Dec, 2012 1 commit
  26. 21 Nov, 2012 1 commit
  27. 05 Sep, 2012 1 commit
  28. 30 Aug, 2012 1 commit
  29. 17 Jul, 2012 1 commit
  30. 22 Jun, 2012 1 commit
    • Do not recursively reindex security unnecessarily · 71e8596e
      In ERP5, objects that do not acquire local roles (according to their portal type configuration) do not need to be reindexed with their containers.
      So do not reindex recursively if portal_types of contained objects don't need it.
      
      Security reindexing can be customized with a type-based method.
      
      Fix test that wrongly relied on unrestricted access for updating object roles.
      Leonardo Rochael Almeida committed
  31. 15 Jun, 2012 1 commit
  32. 03 May, 2012 1 commit
  33. 07 Mar, 2012 1 commit