mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 01:07:15 +03:00
b2aac949cf
Summary: The update of the segmented changelog is light weight enough that we can consider all repositories sharing a common tailer process. With all repositories sharing a single tailer the the maintenance burden will be lower. Things that I am particularly unsure about are: tailer configuration setup and tailer structure. With regards to setup, I am not sure if this is more or less than what production servers do to instantiate. With regards to structure, I think that it makes a lot of sense to have a function that takes a single repo name as parameter but the configuration setup has an influence on the details. I am also unsure how important it is to paralelize the instantiation of the blobrepos. Finally, it is worth mentioning that the SegmentedChangelogTailer waits for `delay` after an update finishes rather than on a period. The benefit is that we don't have large updates taking down a process because we schedule the same large repo update too many timer. The drawback is that scheduling gets messed up over time and multiple repo updates can end up starting at the same time. Reviewed By: farnz Differential Revision: D25100839 fbshipit-source-id: 5fff9f87ba4dc44a17c4a7aaa715d0698b04f5c3 |
||
---|---|---|
.. | ||
fs | ||
integration | ||
locale | ||
mononoke | ||
scm | ||
test_support | ||
test-data | ||
.gitignore | ||
Eden.project.toml |