Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@NeoRazorX esto es que no tengo forma de hacerlo como plugin que era mi idea principal, pero es código muy interno y no creo que sea viable ni con pipes.
la idea es poderlo activar en producción, sin el FS_DEBUG activado.
es para esas instalaciones que se vuelven lentas en producción cuando existen varios usuarios concurrentes y que es dificil de reproducir los fallos o la lentitud en local.
así activas el registro lo dejas algunas horas, dias o minutos y con el csv obtenido ya analizas donde puede estar el cuello de botella.
FS_DEBUG_SQL_TO_FILE se puede activar desde el config.php y tambien desde variables de entorno sin tener que tocar ningun archivo, que en producción puede ser mas atractivo
este es el resultado con formato de tabla en excel y ordenador de mayor duración a menor.