Repo indexer - Max file size

gitea v1.4.0-rc1

I am trying to change the repo indexer max file size. I setted it to 5242880, but the repo file size is fixed to:

Seems that the setting doesn't be load correctly:

I also tried to change the setting, and erased the repo folder, but anyway the size seems to be fixed.

Regards

[lafriks]

MAX_FILE_SIZE is not for index size but for up to how big files to index

Thank you for your fast answer @lafriks . Then, what about the fixed "store" file size? I am trying to indexing a big project, and some of the files was indexed, but seems to be that not everyone, and I supposed that it depends maybe from the "file size"

[lafriks]

how big is file that was not indexed?

Only 9KB, and is a Java file

[lafriks]

Do you see any errors in log file? and why do you think it was not indexed?

No errors in log file. I am sure that the file was not indexed because I am trying to look also for other strings inside this file, but no results appear.

I just replicated the problem. If I create a new repository with just this file and just this repo, then the file is indexed correctly. I think that the problem is the max "store" file size

[lafriks]

I don't think there is maximal size for store file

You can try to replicate the problem by cloning the repo: https://github.com/Xilinx/u-boot-xlnx
and search for string: "dm_test_adc_bind" (that is present in file "test/dm/adc.c"). Even in this case, the store file goes to a size of 1.048.576 KB and stop working (stop to grow up and to index files)

[lafriks]

@ethantkoenig can you check this?

@ethantkoenig @lafriks Thank you. I also want to add an additional information: with the same repository occured also an access violation during repo indexing: Exception

[ethantkoenig]

In my experience, bleve does not do well once index files approach/exceed 1 GB (although it may be different for other machines and OS's). I do recall seeing similar behavior at some point (where an index file remained the exact same size as more content was added to it), but wasn't able to figure out what was going on.

I have found that using sharded indices (not natively supported by bleve) allows bleve to scale more gracefully. Perhaps this is something to consider using in gitea.

Thank you for your answer @ethantkoenig . Are there any workaround to avoid this behavior?

I also want to add some external links to boltdb:
boltdb/bolt#266
boltdb/bolt#308
https://github.com/boltdb/bolt/blob/master/db.go (check comments at row 17, and starting from line 305)
Are those useful?