[Bug]: ClientDB writing absurd amount of data to disk

SoNothingMC commented 8 months ago

Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
[X] I have read the troublshooting FAQs and none solved my issue.

What operating system are you using?

Windows

Build Details

"2.2.0 Wrap Up Build", released 2023-10-18 00:34 GMT

Operating System Version

Windows 10 22H2 (19045.3570)

Describe the Bug

When Cider is launched, it writes a lot of data onto the disk, frequently writing over 500MB. (average value, best case is ~250MB, worse case is ~900MB)

Steps to Reproduce

Launch SysInternals Procexp as administrator
Select "Disk Write Bytes" from View → Select Columns…
Sort the "Process" row alphabetically so processes are shown hierarchically
Launch Cider
See writes to disk from WV2

Library Statistics

Tracks: 4794 (84 imported) Albums: 547 (6 imported) Artists: 274 Playlists: 38 AM playlists, 12 iTunes playlists

Anything else?

After 5mins of playing with ClientDB

After 5mins of playing without ClientDB

Build timestamp

1698160642005

SoNothingMC commented 8 months ago

Note: This was originally made known to me by a user. However, their metrics shows full I/O out of the WV2 process, while mine only shows Disk R/W data. (what they're actually concerned about - writes hurting their SSD)

coredev-uk commented 8 months ago

Every song in your library (inc. playlists) would be written to the database on launch.

coredev-uk commented 7 months ago

ClientDB is being cycled out in favour of a new caching api.

ciderapp / Cider-2