libretro / libretro/RetroArch

slow scanning speed bug still exists on linux

Open
#15,712 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

This old issue (#2381) is still affecting installs today. I'm new to retroarch, but this "fix" vastly improved scanning speeds for me. I'm currently scanning atari 2600 ROM directories. Its taking ~18 hours and still had 10% left. But when I mirrored the steps in this comment, it immediately sped up significantly.

After following this process the scanning takes under an hour. Thats like a 20x improvement. This is NOT trivial, so I'd appreciate someone looking into it.

          Found this:
          - start scanning a big directory, let say all SNES roms
          - launch a NES rom
          - hit space

          Scanning speed unlocked.

Originally posted by @kivutar in https://github.com/libretro/RetroArch/issues/2381#issuecomment-158003634

Can someone please investigate if this is a bug in the default configuration? I do have "gamemode" installed - which is enabled in retroarch.

Version 1.16.0 (89a67e5)

Thats all the info I think is relevant to the issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Linux scanning slowdown with a large ROM directory using the reported version and compare it with launching a NES ROM and pressing space during the scan. Trace the scanning workflow and default configuration to identify why that action changes the speed; done means scanning proceeds at the normal speed without the workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.