Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excalidraw throttling of events #7641

Closed
wants to merge 10 commits into from
Closed

Excalidraw throttling of events #7641

wants to merge 10 commits into from

Conversation

hero101
Copy link
Collaborator

@hero101 hero101 commented Feb 7, 2025

The emission of the following events is throttled, meaning the client sends fewer events, thus less data

  • mouse location events throttled to 10 times per second (30 previously)

  • element mutation events throttled to 100 times per second (200 previously)

  • client will not handle mouse location events until the scene is fully initialized

todo

  • fix version

Summary by CodeRabbit

  • Chores

    • Updated the client package version to a new release variant.
    • Adjusted timing for full scene and cursor updates to refine synchronization frequency.
  • Refactor

    • Enhanced real-time collaboration on the whiteboard by shifting focus to scene initialization.
    • Implemented throttled scene synchronization for more efficient and stable updates.

@hero101 hero101 marked this pull request as draft February 7, 2025 14:40
Copy link

coderabbitai bot commented Feb 7, 2025

Walkthrough

The pull request updates the package version in package.json and refactors the collaboration logic in the Excalidraw module. The changes shift the focus from socket initialization to scene initialization by renaming properties and adjusting methods in both the Collab and Portal classes. Additionally, the synchronization logic now employs a throttled mechanism, and related timing constants have been modified in the constants file.

Changes

File(s) Change Summary
package.json Updated @alkemio/client-web version from "0.82.2" to "0.82.2.ex-perf".
src/.../collab/Collab.ts
src/.../collab/Portal.ts
Refactored initialization logic: renamed socketInitialized to sceneInitilized, removed socketInitializationTimer and initializeRoom, adjusted methods (handleCloseConnection, startCollaboration), and added a throttled scene synchronization method.
src/.../collab/excalidrawAppConstants.ts Modified synchronization constants: doubled SYNC_FULL_SCENE_INTERVAL_MS (5000 → 10000 ms), increased CURSOR_SYNC_TIMEOUT (33 → 100 ms), and added SCENE_SYNC_TIMEOUT set to 10 ms.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Collab
    participant Portal

    User->>Collab: Call syncScene(elements, files)
    Collab->>Collab: Invoke throttledSyncScene(elements, files) [delay: SCENE_SYNC_TIMEOUT]
    Collab->>Portal: Check sceneInitilized and broadcast scene updates
Loading

Possibly Related PRs

Suggested Reviewers

  • bobbykolev
  • ccanos
✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@hero101 hero101 marked this pull request as ready for review February 10, 2025 13:49
@hero101 hero101 requested a review from ccanos February 10, 2025 13:49
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/domain/common/whiteboard/excalidraw/collab/Collab.ts (1)

133-133: Fix typo in property name.

The property name has a typo: sceneInitilized should be sceneInitialized.

-    this.portal.sceneInitilized = false;
+    this.portal.sceneInitialized = false;

Also applies to: 187-187, 200-200

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0b46480 and 7ab0cee.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (4)
  • package.json (1 hunks)
  • src/domain/common/whiteboard/excalidraw/collab/Collab.ts (6 hunks)
  • src/domain/common/whiteboard/excalidraw/collab/Portal.ts (2 hunks)
  • src/domain/common/whiteboard/excalidraw/collab/excalidrawAppConstants.ts (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • package.json
🧰 Additional context used
📓 Path-based instructions (1)
`src/**/*.{ts,tsx,js}`: Review the React.js/TypeScript/JavaS...

src/**/*.{ts,tsx,js}: Review the React.js/TypeScript/JavaScript code for best practices and potential bugs.
Ensure that the code adheres to TypeScript's typing system and modern standards.
Use the following code guide documentation in the codebase: 'docs/code-guidelines.md'.
Ensure sufficient error handling and logging is present, but note:

  • We have a global error handler in place. So local try/catch blocks are not required unless they provide value beyond what the global error handler already covers.
  • Avoid flagging the absence of local error handling in cases where the global error handler suffices.
  • Avoid flagging the absence of logging in cases where the global logger is already in place (graphql usage).

Inform about the recommendation of not using non-null assertion,
except on GraphQL queries where the variable is asserted non-null and followed by a
skip: with the same variable.
Examples:

  • Not Required: there's a skip
    {
    variables: { templateId: templateId! },
    skip: !templateId,
    }

Check for common security vulnerabilities such as:

  • SQL Injection
  • XSS (Cross-Site Scripting)
  • CSRF (Cross-Site Request Forgery)
  • Insecure dependencies
  • Sensitive data exposure
  • src/domain/common/whiteboard/excalidraw/collab/Portal.ts
  • src/domain/common/whiteboard/excalidraw/collab/excalidrawAppConstants.ts
  • src/domain/common/whiteboard/excalidraw/collab/Collab.ts
🔇 Additional comments (4)
src/domain/common/whiteboard/excalidraw/collab/excalidrawAppConstants.ts (1)

44-47: LGTM! Performance optimization through throttling.

The timing adjustments effectively reduce event frequency:

  • Mouse location updates throttled to 10fps (100ms) from ~30fps
  • Full scene sync interval doubled to 10 seconds
  • Scene updates throttled to 10ms intervals
src/domain/common/whiteboard/excalidraw/collab/Portal.ts (1)

46-46: LGTM! Improved semantic naming.

Renaming socketInitialized to sceneInitilized better reflects that we're waiting for scene initialization, not just socket connection.

src/domain/common/whiteboard/excalidraw/collab/Collab.ts (2)

426-442: LGTM! Well-implemented throttling mechanism.

The throttling implementation effectively reduces scene update frequency while maintaining data consistency through version tracking.


218-228: LGTM! Optimized event handling.

Good optimization to prevent mouse location handling until scene initialization is complete, which can improve loading times.

@hero101 hero101 changed the base branch from develop to release/release-9-patch-2 February 10, 2025 13:58
@hero101 hero101 changed the base branch from release/release-9-patch-2 to develop February 10, 2025 13:58
@hero101 hero101 mentioned this pull request Feb 10, 2025
@bobbykolev
Copy link
Collaborator

merged as part of release 10

@bobbykolev bobbykolev closed this Feb 12, 2025
@bobbykolev bobbykolev deleted the excalidraw-perf branch February 12, 2025 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants