Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinuxsavoirfairelinux
  • jami-client-gnome
  • Issues
  • #833

chatview: major efficiency issues in updateTimestamps

updateTimestamps() is affected by several design issues with a large drawbacks on performances:

  1. This function goes through all timestamp entries and is called by addOrUpdateMessage(). This means that this function is called each and every time a message is displayed ! This is basically O(n²) algorithm. For instance, displaying 50 messages triggers 1275 timestamp updates.
  2. This function handles both text and position/style updates. The is probably done in order to simulate some kind of responsive behaviour. This should be done by CSS, not JS.
Assignee
Assign to
Time tracking