OneDev performs full text index of commit of the repository when the commit is visited. In normal cases, the index should not be so large if the repository itself is not very large. I can test the repository if this is publicly available.

Thank you!

Wine repository: https://git.houseof.software/WineHQ/Wine Linux repository: https://git.houseof.software/torvalds/linux

I kept them mostly for benchmarking purposes, since the creation of the OneDev instance last year.

Did perhaps something change regarding the index in OneDev 16.6? Because the virtual disk I assigned to the container became full two days after updating from 16.5.8 to 16.6.1.

Nothing changed regarding repository indexing since 16.5.8. I checked Wine and the index on tip commit is only 450k. I guess your large index is because it indexed lots of history commits which may happen if someone or some UI automation tools visited many history commits triggering the index.

Nevertheless, you may stop OneDev and remove the index folder. It will not hurt OneDev functionality, just that it will be re-indexed when someone visited some commit of that repo later.

Makes perfect sense, thank you!

Could you perhaps add a per-repository and/or global index size limit?

It is difficult to limit index size, but we can add settings to control whether or not create index, and what type of index to create: OD-3124

Sounds good!