...
ZENDSVR6 for version 6 - 8.5.x
If Code Tracing is enabled for one or more very common events, then code trace dumps can accumulate very quickly, and reach unmanageable levels. Code Tracing is meant to be a diagnostic tool, and in general should not be routinely enabled for events in a production environment. Instead, Code Tracing should be enabled for an event type that is under active investigation, and should be disabled when the investigation is concluded. The following steps can help you clear the code trace dumps and data base if too many accumulate for manual deletion.
Note: This procedure requires a restart of Zend Server, so your web site will be down for a few minutes. Please schedule this activity for a time when the service disruption will have the minimum impact.
1. (Optional) Consider disabling Code Tracing for Monitor Events, to prevent proliferation of excess Code Trace dumps. This setting can be used later to turn Code Tracing On and Off only as needed to research issues. In the Zend Server Administrative interface, go to the Configurations -> Monitor tab. Under the heading "Code Tracing Settings", select the "Disable Code Tracing" button. Click the "Save" button to save the change. Do not restart the PHP server at this time, it will be done in a later step.
...