Free dvd profiler software for linux

This profiler is intended to be used to identify areas of code that could be optimised in order to improve overall performance of an application. Typically I identify the areas of concern in an application and place profile timers around those sections and focus down to add timers around the areas that are taking the most time and look for ways to optimise those particular areas.
The items with the highest percentage time spent are usually the ones that can give the biggest improvements.
PHP Class to perform code profiling in order to aid locating areas of code that consume most processing time.
Provides information on number of calls to a code section, percentage and total of time spent on a section. Timing of nested code sections is possible.
Main features:
- Count the number of times a section of code is executed
- Calculate the total ammount of time spent executing a section of code
- Permit multiple timers to be set
- Allow nested timers to such that the parent timers are suspended whilst a child section of code is running.
- Output a report at the end of execution to show the percentage of time spent on an operation,
- the number of times the section was run, the overall time spent on the section.
Usage:
# include_once( profiler.inc);
$prof = new Profiler( profile_flag, trace_flag );
# Profile_flag = true enables output of the statistical information
# trace_flag = true enables output of the trace information
$prof->startTimer( "timer_name", "Description" );
# timer_name is a simple string to name the timer
# description is an optional string to describe the purpose of the timer in more detail
$prof->stopTimer( "timer_name" );
$prof->printTimers( flag );
Output the final report of the processing operation being run. Normally this would be called as one of the last statements on a page.
If flag=true is set then the output will be forced even if the profile_flag was set false when the profiler was initialised

FProfiler project is a Java profiler for finding hotspots in Java libs/apps.
FProfiler is a Java Profiler using BCEL and log4j.
Its very fast because it inserts the needed instructions into the Bytecode of the classes. It can be used to find Hotspots in Java programs, libs, and servlet environments--simply every Java class.
Enhancements:
- Mark Atwell fixed a bug with are branch (jump/goto) instructions directly to the return statement bypassing the stop call.

phpMyProfiler is based on myprofiler and parses the XML files of DVD Profiler (www.intervocative.com) to insert information into a MySQL database.
Compared to the service of Intervocative, the layout is configurable and almost all information about your DVD collection can be provided.
Additional features include a newsletter, a guestbook, loan management, a cover gallery, and reports.
Enhancements:
- new: Support for addicted2dvds TV Series Episode Guides
- new: Added selection for ownership state in report
- new: Added Cast&Crew Gallery. Thanks to Sundance
- new: Danish translation. Thanks to thezubdk
- new: Added search for audio languages and rating
- new: New theme deviant. Thanks to George Lewe
- fix: closed security hole in functions.php

Profiler4j is a Java CPU profiler 100% portable. Profiler4js primary goal is to be simple to use by allowing sofisticated UI interactions. If youre unpatient like me, just jump to the getting started section or see some screenshots.
But please keep in mind that this project is in early development stage and may have some nasty bugs. Also, I plan to add much more features in the next releases.
Main features:
- Based on dynamic bytecode instrumentation.
- 100% Java.
- Simple deployment -- just add a parameter to the command line and youre ready to go.
- Remote console to view and analyze results. Currently two view modes are supported:
- Graph view (already functional) similar to JProbe.
- Call tree view (in progress)
- Fine-grained configuration that can be freely tuned without restarting the profiled JVM.
Version restrictions:
- Call Tree View still has some bugs with recursive methods (seems ok since 1.0-alpha4)
- Core java classes (java.*, javax.*) and some other packages (org.xml.*, org.jaxen.*, etc.) are not profiled.
- Constructors are not profiled. Thats a minor problem because most of the work is done by other methods anyway.
- Heavy memory usage when the target application has many threads. Not really a bug but I think it must be noted. You can provide rules to instrument only the classes you really need to.

KungFu DVD Ripper is a GStreamer based DVD ripper.

KungFu creates backups of your DVDs, saving them as .oggs on your hard drive. It encodes the backup using patent-free codecs, Theora for video and Vorbis for audio.

KungFu is not designed for producing backups that fit within a certain file size (say, for burning onto CD); instead, it is designed to produce backups of consistent quality while maintaining the lowest average file size possible (for building a video library on your hard drive).

DVD BacKup Express is a small Kommander Script to create a GUI for dvdbackup.

I made it because it can be run on any platform with kommander installed and dvdbackup available (which may be more platforms than kdvdbackup or other binary frontends are available for)

There is a lot of room for improvement here. Feel free to spruce it up a bit and send me the new .kmdr file and i will update this.

Devel::DProf is a Perl code profiler.

SYNOPSIS

perl5 -d:DProf test.pl

The Devel::DProf package is a Perl code profiler. This will collect information on the execution time of a Perl script and of the subs in that script. This information can be used to determine which subroutines are using the most time and which subroutines are being called most often. This information can also be used to create an execution graph of the script, showing subroutine relationships.
To profile a Perl script run the perl interpreter with the -d debugging switch. The profiler uses the debugging hooks. So to profile script test.pl the following command should be used:

perl5 -d:DProf test.pl

When the script terminates (or when the output buffer is filled) the profiler will dump the profile information to a file called tmon.out. A tool like dprofpp can be used to interpret the information which is in that profile. The following command will print the top 15 subroutines which used the most time:

dprofpp

To print an execution graph of the subroutines in the script use the following command:

dprofpp -T

Consult dprofpp for other options.

PROFILE FORMAT

The old profile is a text file which looks like this:

#fOrTyTwO
$hz=100;
$XS_VERSION=DProf 19970606;
# All values are given in HZ
$rrun_utime=2; $rrun_stime=0; $rrun_rtime=7
PART2
+ 26 28 566822884 DynaLoader::import
- 26 28 566822884 DynaLoader::import
+ 27 28 566822885 main::bar
- 27 28 566822886 main::bar
+ 27 28 566822886 main::baz
+ 27 28 566822887 main::bar
- 27 28 566822888 main::bar
[....]

The first line is the magic number. The second line is the hertz value, or clock ticks, of the machine where the profile was collected. The third line is the name and version identifier of the tool which created the profile. The fourth line is a comment. The fifth line contains three variables holding the user time, system time, and realtime of the process while it was being profiled. The sixth line indicates the beginning of the sub entry/exit profile section.

The columns in PART2 are:

sub entry(+)/exit(-) mark
apps user time at sub entry/exit mark, in ticks
apps system time at sub entry/exit mark, in ticks
apps realtime at sub entry/exit mark, in ticks
fully-qualified sub name, when possible

With newer perls another format is used, which may look like this:

#fOrTyTwO
$hz=10000;
$XS_VERSION=DProf 19971213;
# All values are given in HZ
$over_utime=5917; $over_stime=0; $over_rtime=5917;
$over_tests=10000;
$rrun_utime=1284; $rrun_stime=0; $rrun_rtime=1284;
$total_marks=6;

PART2
@ 406 0 406
& 2 main bar
+ 2
@ 456 0 456
- 2
@ 1 0 1
& 3 main baz
+ 3
@ 141 0 141
+ 2
@ 141 0 141
- 2
@ 1 0 1
& 4 main foo
+ 4
@ 142 0 142
+ & Devel::DProf::write
@ 5 0 5
- & Devel::DProf::write

(with high value of $ENV{PERL_DPROF_TICKS}).

New $over_* values show the measured overhead of making $over_tests calls to the profiler These values are used by the profiler to subtract the overhead from the runtimes.

The lines starting with @ mark time passed from the previous @ line. The lines starting with & introduce new subroutine id and show the package and the subroutine name of this id. Lines starting with +, - and * mark entering and exit of subroutines by ids, and goto ⊂r.

The old-style +- and --lines are used to mark the overhead related to writing to profiler-output file.