Library and Archive: opening or saving a small text file takes 1 to 6 seconds

Aperta
#501 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Start by profiling library-object reads and writes and the eight sidebar folder-list requests made during each Library window load. Check whether the folder lists are handled one at a time, and review #445 for the related cost of decrypting every file in a folder. Done means small text files open and save about as fast as in Documents, and the visible folder loads before the others.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

The ElastOS User Tester measured this on 0.8.0-alpha.25 (source 92aeea44d) on 28 Oct 2026, three runs each, with a 44-byte .txt file:

  • Library opened the file in Documents in about 1.5 s and saved it in about 0.9 s. Each library-object read or write took about 1 s.
  • Archive took about 6.4 s to make a ZIP of that file and about 4.4 s to open the ZIP.
  • For comparison, Documents saved its own file in about 60 ms.

Each Library window load, including the picker that Archive uses, asks for the lists of eight sidebar folders at the same moment. The last list returned after about 3 s, and an action the person took right after it waited behind them. The tester did not check whether the server answers these lists one at a time.

Expected: a small file opens and saves about as fast as in Documents, and Library loads the folder the person sees before the others. A good first step is to profile library-object and the folder lists. #445 (a folder listing decrypts every file in the folder) may explain part of the time.

The 0.8.0 candidate has no change for this, and the timings were not measured again on it.

Lingua principale
Rust
Stelle
6
Fork
2
Merge medio
1g 3h
PR unite (30g)
42

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di elastos/elastos-runtime

Tutte le issue di elastos/elastos-runtime

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.