You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
There are multiple issues with that stack:
* glean CI is broken (and we don't now how to fix it) 3867100#commitcomment-172635196
* It degraded the time of fillOwnership processing
* We really need to test `configerator` db first, because we use chronos write server there and the complete step already takes 37 GB. (see the spike on memory usage https://www.internalfb.com/chronos/job_instance/gp/81064803470734278/info). And having u64 sets will only increase it.
* I face a crash trying to connect to the db which was produced with this change: `test.1/1: couldn't open: corrupt database - invalid FIRST_UNIT_ID`
* There are also couple of comments from Simon Marlow about not using justknob in `database` target and using a db version for controlling the format.
So, given all that we have to revert it before it publishes on Monday. After that I think we don't need to move to U64 format at all, just change TrieArray implementation with proper profiling.
Reviewed By: jjuliamolin, phlalx
Differential Revision: D89051067
fbshipit-source-id: 0c6858ab1ffd42b8d2d6d33a5d2e795d3b40bf41
0 commit comments