Comment 5 for bug 2060804

Various invocations of `juju debug-log` such as `juju debug-log --replay` are going to have to iterate through all of that data. Things like the automatic pruning to keep the log table at reasonable sizes are also going to be impacted by larger collections.

IIRC, `model-logs-size` is per-model. So setting it to 20G means that you will have 20G * N models (eg in Prodstack that will be 20*300 = 1.2TB.)

But for CI that shouldn't be inherently problematic.

Note that you can already set a syslog forwarder and put it into a system for actually handling large amounts of logs, rather than just `juju debug-log`.