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
Currently, llbuild stores the full key for all dependencies in the database. On a large project like LLVM, this leads to a lot of redundancy because individual dependencies (e.g., a header file) are repeated a large number of times.
This is particularly redundant because almost all keys have a corresponding rule which embeds the name as well.
We should move to storing the dependency indirectly via an ID to the rule. I forget the exact numbers, but this reduces the dependency database for LLVM by a very large mount (IIRC, around 80%).
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: d6933d9eaccb9e5c54c85a636c38c3db
Issue Description:
Currently, llbuild stores the full key for all dependencies in the database. On a large project like LLVM, this leads to a lot of redundancy because individual dependencies (e.g., a header file) are repeated a large number of times.
This is particularly redundant because almost all keys have a corresponding rule which embeds the name as well.
We should move to storing the dependency indirectly via an ID to the rule. I forget the exact numbers, but this reduces the dependency database for LLVM by a very large mount (IIRC, around 80%).
The text was updated successfully, but these errors were encountered: