Fossilize influenced by I/O load on unrelated drives
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- performance
Research direction
Reproduce Vulkan shader processing while transferring files between the two unrelated RAID mounts described in the report. Start by tracing Fossilize's processing and I/O behavior during that transfer; done means processing continues at full use instead of stopping until the transfer is paused or completed.
Written by the indexing model from the issue text.
Description
Your system information
- Steam client version (build number or date): latest (Jan 16 2022)
- Distribution (e.g. Ubuntu): Gentoo
- Opted into Steam client beta?: [Yes/No] No
- Have you checked for system updates?: [Yes/No] Yes
Hardware:
3900x
64GB RAM
Rest described below.
When using the following setup with an I/O load fossilize will go down from maxing my processor to using only one core at 50% to having no CPU usage at all.
Setup:
BTRFS RAID0 (2x512GB /)
BTRFS RAID0 (2x10TB /mnt/RAID)
BTRFS Single drive (1x3TB /mnt/RAID/3TB)
Have steam install and download games in /home/user
How to replicate:
Start processing vulkan shaders;
Start transferring files from /mnt/RAID/3TB to /mnt/RAID (this shouldn't cause any problems as the I/O is not on the main drive).
Fossilize now vanishes from system and stops working until the transfer is completed, cancelled or paused.
Reason for bug:
The I/O is not on the main drive that steam is installed on, so it shouldn't affect fossilize. On my 3900x the load average is 3. Plenty of CPU for fossilize to run.
Pausing the transfer results in the CPU suddenly hitting 100% with fossilize using all cores after a second or two.
- Dominant language
- C++
- Stars
- 780
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ValveSoftware/Fossilize
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ValveSoftware/Fossilize#312 · 1 comment · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ValveSoftware/Fossilize#306 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ValveSoftware/Fossilize#303 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ValveSoftware/Fossilize#300 · 6 comments · 4 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
ValveSoftware/Fossilize#296 ·
All issues in ValveSoftware/Fossilize
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·