Skip to content
RhodeCode
← All customer stories
Research computing

Search that kept working as the repository count grew

A national research institute had repositories per grant, per student and per experiment.

Indexed full-text search, filtered by what each user may read
Fig. 04 Indexed full-text search, filtered by what each user may read
Repositories
40k
Users
2,000
Licence
CE
02.1Challenge

Forty thousand repositories nobody could search.

After fifteen years the institute had roughly forty thousand repositories, and the practical consequence was that prior work could not be found.

So it was rewritten. Researchers reimplemented solvers that already existed two directories away — the most expensive failure mode in research software, and invisible on any dashboard.

02.2Approach

Index everything, filter by permission.

Full-text search was indexed across every repository, file, commit message, comment and snippet, on its own storage volume so rebuilds never contend with repository I/O.

Results are filtered by the permissions of whoever is searching, which let the institute index restricted projects alongside open ones instead of excluding them.

People read what already exists before they start now. That was not true before, at any scale.
Engineering lead · name withheld
02.3Results

Two thousand users, on the free edition.

Measured afterwards
  1. 0040,000 repositories under a single index
  2. 012,000 users served by the Community Edition
  3. 02Search results filtered per searcher, not per project
  4. 03Mercurial retained for legacy pipelines

Mercurial repositories stayed on Mercurial for the legacy pipelines that depend on them, under the same permission model as the Git projects beside them.

Would this approach fit your organisation?

Bring your repository count, your VCS mix and your compliance constraints. We will tell you honestly whether a staged migration is the right answer for you — sometimes it is not.

Bring
repository count, VCS mix, seat count
Constraints
regulator, classification, contract
We answer
within 24 hours, by an engineer
Contact
sales@rhodecode.com