[Discussion]: High CPU Usage When Backing Up Data to S3-Compatible Storage · CherryHQ/cherry-studio#12984

2026-02-21T05:26:57.000Z

### Issue Checklist - [x] 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. - [x] I have checked the pinned issues and searched through the existing [open issues](https://github.com/CherryHQ/cherry-studio/issues), [closed issues](https://github.com/CherryHQ/cherry-studio/issues?q=is%3Aissue%20state%3Aclosed), and [discussions](https://github.com/CherryHQ/cherry-studio/discussions) and did not find a similar suggestion. - [x] 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 ```shell ``` ### Priority Low (Review when available)

(3 commenti) (1 reazione) (1 assegnatario)TypeScript (4338 fork)batch import

Datadiscussionhelp wanted

Metriche repository

Star: (45.688 star)
Metriche merge PR: (Merge medio 4g 23h) (199 PR mergiate in 30 g)

Descrizione

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)

Guida contributor

Direzione di ricerca: Esegui il profiling dell'uso della CPU durante il backup su S3 per identificare i punti critici. Verifica la presenza di loop inefficienti, allocazioni di memoria eccessive o I/O bloccante. Considera l'uso di streaming asincrono o batch. Rivedi l'implementazione del backup nel codebase.
Tech stack: Nessuno
Dominio: backend
Tipo issue: Ricerca
Difficoltà: 2
Tempo stimato: 1-3 ore
Stato attività: Attiva
Chiarezza: Richiede indagine
Prerequisiti: Nessuno
Adatta ai principianti: 70