Skip to content

Commit 7ecab8d

Browse files
joshtrichardsbackportbot[bot]
authored andcommitted
docs(config): clarify metadata and conversion file size limits
- correct unit for metadata_max_filesize to match implementation (MiB) - wording/clarity including resource impact Signed-off-by: Josh <josh.t.richards@gmail.com>
1 parent a4189dc commit 7ecab8d

1 file changed

Lines changed: 13 additions & 6 deletions

File tree

config/config.sample.php

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1608,20 +1608,27 @@
16081608
],
16091609

16101610
/**
1611-
* Maximum file size for metadata generation.
1612-
* If a file exceeds this size, metadata generation will be skipped.
1611+
* Maximum file size for file metadata generation.
16131612
*
1614-
* NOTE: memory equivalent to this size will be used for metadata generation.
1613+
* Files larger than this limit will be skipped.
16151614
*
1616-
* Default: 256 megabytes.
1615+
* This limit helps bound resource usage during metadata generation. Actual
1616+
* resource usage depends on the active metadata providers and how they
1617+
* process files. As a rough guide, memory usage may scale with file size.
1618+
*
1619+
* Default: 256 MiB.
16171620
*/
16181621
'metadata_max_filesize' => 256,
16191622

16201623
/**
16211624
* Maximum file size for file conversion.
1622-
* If a file exceeds this size, the file will not be converted.
16231625
*
1624-
* Default: 100 MiB
1626+
* Files larger than this limit will be skipped.
1627+
*
1628+
* Raising this limit may increase conversion time, resource usage, and the
1629+
* risk of timeouts or conversion failures depending on the provider.
1630+
*
1631+
* Default: 100 MiB.
16251632
*/
16261633
'max_file_conversion_filesize' => 100,
16271634

0 commit comments

Comments
 (0)