Skip to content

Commit 36854f6

Browse files
Add section about the impact of "--skip-references"
1 parent 76c9489 commit 36854f6

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

UnityDataTool/Commands/analyze.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,3 +112,23 @@ These errors occur when the same serialized file name appears in multiple source
112112

113113
See [Comparing Builds](../../Documentation/comparing-builds.md) for strategies to compare different versions of builds.
114114

115+
### Slow Analyze times and big database
116+
117+
Consider using the `--skip-references` argument.
118+
119+
As an example of how big a difference this casen make: one large Addressables project took 208 seconds and producted a 500MB database.
120+
With --skip-references the same analyze call took 9 seconds and produced a 68 MB file.
121+
122+
The references are not needed for core asset inventory and size information.
123+
124+
When specifying --skip-reference some functionality is lost:
125+
126+
* the `find-refs` command will not work
127+
* `view_material_shader_refs` and `view_material_texture_refs` will be empty
128+
* Queries that look at the relationship between objects will not work. For example the refs table is required to link between a `MonoBehaviour` and its `MonoScript`.
129+
* The `objects.crc32` column will be NULL/0 for all objects. This means:
130+
* No detection of identical objects by content hash (See [Comparing Builds](../../Documentation/comparing-builds.md))
131+
* The `view_potential_duplicates` view relies partially on CRC32 to distinguish true duplicates
132+
133+
Future work: The refs table could be made smaller and more efficient. It might also be prudent to control the CRC32 calculation using an independent flag.
134+

0 commit comments

Comments
 (0)