CherryHQ/cherry-studio

[Discussion]: High CPU Usage When Backing Up Data to S3-Compatible Storage

Open

#12984 opened on Feb 21, 2026

View on GitHub
 (3 comments) (1 reaction) (1 assignee)TypeScript (45,688 stars) (4,338 forks)batch import
Datadiscussionhelp wanted

Description

Issue Checklist

  • I understand that issues are meant for feedback and problem-solving, not for venting, and I will provide as much detail as possible to help resolve the issue.
  • I have checked the pinned issues and searched through the existing open issues, closed issues, and discussions and did not find a similar suggestion.
  • I confirm that I am here to ask questions and discuss issues, not to report bugs or request features.

Platform

Windows

Version

1.7.19

Your Question

Noticed that backing up data to S3-compatible storage consumes a significant amount of CPU resources. Is this normal?

Context

No response

Additional Information

Priority

Low (Review when available)

Contributor guide

Tech stack
typescriptnodejsaws
Domain
backendperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.js basicsS3 storage understandingCherry Studio codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by examining the backup module in the Cherry Studio codebase, likely under src/backup or similar. Look for S3 client initialization and the data transfer loop. Profile CPU usage during a backup operation to identify the bottleneck. Check existing comments or maintainer responses for hints about known performance issues.