Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • erp5 erp5
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 142
    • Merge requests 142
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedinexedi
  • erp5erp5
  • Merge requests
  • !614
The source project of this merge request has been removed.

ERP5Type/Base.py: Store a result of getCreationDate and returns it next time.

Closed Yusei Tahara requested to merge (removed):master into master Mar 20, 2018
  • Overview 24
  • Pipelines 0
  • Changes 1

Otherwise if there is a very long history, getCreationDate becomes slow because of append-optimized data structure of WorkflowHistoryList.

According to Rafael, it already happens in SlapOS master. In my test environment, I created an object that has 470,000 lines of history of edit_workflow and it takes more than 50 seconds to call getCreationDate.

@vpelletier @jm

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: master
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7