Miva - Performance Profiling and Diagnostics with diagtool.mvc
diagtool.mvc
. It's likely in a folder like:
mivavm-v5.36/tools/diagtool.mvc
diagtool.mvc
file to the web-root directory (Typically that would be at: /httpdocs/diagtool.mvc
)./cgi-bin/mivavm.conf
file with the following logging settings (View this miva.com/forum post for other log-level options).logfile=diagtool.log
loglevel=144
logcookie=diagtool
https://www.yourdomain.com/diagtool.mvc
./private/mivadata/diagtool.log
. Note that the log file will be appended to for each page tested. It is generally recommended to download the log file locally, and then delete it from the server after each page visit to separate the page results.mvprof
command in your terminal. View the syntax and options on this miva.com/forum post. Note that this command may change depending on installation of the mvprof tool, however, it is recommended to add the path for the tool to the global path for your OS. Once the global path is set, you should be able to run the following terminal command:$ mvprof -output <path/for/outputfile> <path/for/inputfile>
Example (Mac or Unix):
$ cd ~/path/to/diagtool.log
$ mvprof -output diagtool_results.txt diagtool.log
https://www.yourdomain.com/diagtool.mvc
, and click the REMOVE TOOL FROM SERVER option./cgi-bin/mivavm.conf
by removing or commenting out the log settings that were added earlier (logfile
, loglevel
, & logcookie
).Special Thanks to Patrick Stearns for contributing to this doc and adding more detailed steps.