In our experience, this happens at around 80 log files, but like all things related to memory usage/fragmentation the behaviour non-deterministic.
Things that break when the file list fails to allocate or consumes all available memory:
- All data on the
status.htm webpage (since the status message includes the full file list)
- The status table on
index.htm webpage (for the same reason as above)
- Downloading the file list on the status webpage
- Downloading all logs zipped together (although this one probably isn't going to work with a large number of log files anyway)
- Auto upload of files. Making an SSL connection requires a few large chunks of contiguous memory and is quite susceptible to memory exhaustion/fragmentation.
In our experience, this happens at around 80 log files, but like all things related to memory usage/fragmentation the behaviour non-deterministic.
Things that break when the file list fails to allocate or consumes all available memory:
status.htmwebpage (since the status message includes the full file list)index.htmwebpage (for the same reason as above)