mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 16:31:02 +03:00
757ac0028e
Summary: Logging all these throttling notifications is not necessary. There can sometimes be big batches of fetches (like 100s of K). Lets reduce this by a factor of 1000. Note we also would like to add logging of what process triggered these fetches what endpoint they use etc. This will help us identify the workflows causing it, so we could address them or skip aux data fetching in these code paths. But this requires some fiddling with ObjectFetchContext and the logging code, so its gonna take a bit longer :( Reviewed By: genevievehelsel Differential Revision: D25505654 fbshipit-source-id: e7c40164db86fadf4baf0afd0c52879e0cb2568b |
||
|---|---|---|
| .. | ||
| benchharness | ||
| benchmarks | ||
| cli | ||
| config | ||
| docs | ||
| fuse | ||
| inodes | ||
| journal | ||
| model | ||
| monitor | ||
| nfs/xdr | ||
| notifications | ||
| prjfs | ||
| py | ||
| rocksdb | ||
| scripts | ||
| service | ||
| sqlite | ||
| store | ||
| takeover | ||
| telemetry | ||
| testharness | ||
| third-party | ||
| utils | ||
| CMakeLists.txt | ||