Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

data::objectdriver::profiler(3pm) [debian man page]

Data::ObjectDriver::Profiler(3pm)			User Contributed Perl Documentation			 Data::ObjectDriver::Profiler(3pm)

NAME
Data::ObjectDriver::Profiler - Query profiling SYNOPSIS
my $profiler = Data::ObjectDriver->profiler; my $stats = $profiler->statistics; my $total = $stats->{'DBI:total_queries'}; my $log = $profiler->query_log; $profiler->reset; USAGE
$Data::ObjectDriver::PROFILE To turn on profiling, set $Data::ObjectDriver::PROFILE to a true value. Alternatively, you can set the DOD_PROFILE environment variable to a true value before starting your application. Data::ObjectDriver->profiler Profiling is global to Data::ObjectDriver, so the Profiler object is a global instance variable. To get it, call Data::ObjectDriver->profiler, which returns a Data::ObjectDriver::Profiler object. $profiler->statistics Returns a hash reference of statistics about the queries that have been executed. $profiler->query_log Returns a reference to an array of SQL queries as they were handed off to DBI. This means that placeholder variables are not substituted, so you'll end up with queries in the query log like "SELECT title, difficulty FROM recipe WHERE recipe_id = ?". $profiler->query_frequency Returns a reference to a hash containing, as keys, all of the SQL statements in the query log, where the value for each of the keys is a number representing the number of times the query was executed. $profiler->reset Resets the statistics and the query log. $profiler->total_queries Returns the total number of queries currently logged in the profiler. $profiler->report_queries_by_type Returns a string containing a pretty report of information about the current number of each type of query in the profiler (e.g. "SELECT", "INSERT"). $profiler->report_query_frequency Returns a string containing a pretty report of information about the current query frequency information in the profiler. perl v5.12.4 2011-08-29 Data::ObjectDriver::Profiler(3pm)

Check Out this Related Man Page

asadmin-delete-profiler(1AS)					   User Commands				      asadmin-delete-profiler(1AS)

NAME
asadmin-delete-profiler, delete-profiler - deletes the profiler element SYNOPSIS
delete-profiler --user admin_user [--password admin_password] [--host localhost] [--port 4848] [--secure|-s] [--passwordfile filename] [--terse=false] [--echo=false] [--interactive=true] Deletes the profiler element. A server instance is tied to a particular profiler by the profiler element in the Java configuration. Chang- ing a profiler requires you to restart the server. This command is supported in remote mode only. OPTIONS
--user authorized domain application server administrative username. --password password to administer the domain application server. --host machine name where the domain application server is running. --port port number of the domain application server listening for administration requests. --secure if true, uses SSL/TLS to communicate with the domain application server. --passwordfile file containing the domain application server password. --terse indicates that any output data must be very concise, typically avoiding human-friendly sentences and favoring well- formatted data for consumption by a script. Default is false. --echo setting to true will echo the command line statement on the standard output. Default is false. --interactive if set to true (default), only the required password options are prompted. Example 1: Using delete-profiler asadmin> delete-profiler --user admin --passwordfile passwords.txt --host localhost --port 4848 Deleted Profiler Where: profiler is the deleted profile element. EXIT STATUS
0 command executed successfully 1 error in executing the command asadmin-create-profiler(1AS), asadmin-list-profiler(1AS) J2EE 1.4 SDK March 2004 asadmin-delete-profiler(1AS)
Man Page