Skip to main content
improve edits
Source Link

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHProf or XDebug and find the guilty code. XHProf (a profiler) draws you a nice map of all the functions that are being executed on the server, and it tells you which ones are consuming the most execution time to execute. On the other hand, when XDebug (a debugger) is configured with an IDE such as Eclipse (see video) it allows you drill down into every function being executed LIVE. The profiler will give you an idea of what is being executed; while the debugger will show you why is it being executed.

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHProf or XDebug and find the guilty code. XHProf (a profiler) draws you a nice map of all the functions that are being executed on the server, and it tells you which ones are consuming the most time to execute. On the other hand, XDebug (a debugger) allows you drill down into every function being executed LIVE. The profiler will give you an idea of what is being executed; while the debugger will show you why is it being executed.

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHProf or XDebug and find the guilty code. XHProf (a profiler) draws you a nice map of all the functions that are being executed on the server, and it tells you which ones are consuming the most execution time. On the other hand, when XDebug (a debugger) is configured with an IDE such as Eclipse (see video) it allows you drill down into every function being executed LIVE. The profiler will give you an idea of what is being executed; while the debugger will show you why is it being executed.

Added links, and brief explanation of the technologies suggested.
Source Link

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHProfXHProf or XDebugXDebug and find the guilty code. XHProf (a profiler) draws you a nice map of all the functions that are being executed on the server, and it tells you which ones are consuming the most time to execute. On the other hand, XDebug (a debugger) allows you drill down into every function being executed LIVE. The profiler will give you an idea of what is being executed; while the debugger will show you why is it being executed.

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHProf or XDebug and find the guilty code.

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHProf or XDebug and find the guilty code. XHProf (a profiler) draws you a nice map of all the functions that are being executed on the server, and it tells you which ones are consuming the most time to execute. On the other hand, XDebug (a debugger) allows you drill down into every function being executed LIVE. The profiler will give you an idea of what is being executed; while the debugger will show you why is it being executed.

edited body
Source Link
Berdir
  • 83.5k
  • 6
  • 161
  • 207

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHPerfXHProf or XDebug and find the guilty code.

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHPerf or XDebug and find the guilty code.

The Devel module offers database logging to check whether you have any long running queries.

If this doesn't help take either XHProf or XDebug and find the guilty code.

Source Link
BetaRide
  • 5.4k
  • 22
  • 32
Loading