remotefilelog: Large Manifest

[Son Luong Ngoc]

Just to add some more info:
The repo was convert from git -> hg using hg-git latest version(Cloned from Heptapod) and HG 5.2.2 (or 5.2.1)

The following is the debug info:
> hg debugformat
format-variant    repo
fncache:           yes
dotencode:         yes
generaldelta:      yes
sparserevlog:      yes
sidedata:           no
copies-sdc:         no
plain-cl-delta:    yes
compression:       zlib
compression-level: default

My current hypothesis is that because this repo was converted from git with hg-git: 
- too many HEADs/Branches
- a non-linear history because of "merge commit"

I would appreciate if somebody could give me a hint on how to deal with this case :(

Cheers,
Son Luong.

> On Feb 21, 2020, at 18:13, Son Luong Ngoc <son.luong at booking.com> wrote:
> 
> Hey folks,
> 
> Another question tinkering with RemoteFileLog extension is how to deal with large number of changelog and manifest?
> In particular, this is my current store after shallow cloning with RemoteFileLog (on a large repo, total clone time is ~20 mins) 
> 
> ~/test/repo-hg/.hg/store> du -sh ./*
> 304M    ./00changelog.d
> 81M    ./00changelog.i
> 1.8G    ./00manifest.d
> 80M    ./00manifest.i
>  0B    ./data
>  0B    ./phaseroots
> 4.0K    ./undo
> 4.0K    ./undo.backupfiles
>  0B    ./undo.phaseroots
> 
> Client side config
> ~> cat ~/.hgrc
>  [extensions]
>  remotefilelog =
>  fsmonitor =
>  sparse =
> 
>  [remotefilelog]
>  cachepath = /Users/sluongngoc/test/hgcache
>  cachelimit = 10
> 
> Serverside config
> 
>> cat .hg/hgrc
> [paths]
> # HG-Git stuff
> default = git+ssh://git@gitserver/path/repo.git
> 
> [remotefilelog]
> server = True
> serverexpiration = 10
> 
> Thanks,
> Son Luong.