Free profiling software for linux

AutoProfile is an extension to Gaim that allows users to create customized away messages and profiles using dynamic "components" that automatically update on a regular basis.
Generated text can include song names from XMMS/Winamp/iTunes, fortune quotes, computer uptime, the contents of a Web page or a text file, the output of a program, and timestamps.
AutoProfile plugin comes complete with a graphical preference system that covers a wide range of options and lets users choose exactly how they want their profiles to behave. The code is Open Source (licensed under the GPL) and designed such that it is extremely easy for users to extend the capabilities of this plugin.
Enhancements:
- This version is updated to work with Gaim 2.0.0 beta3.
- Minor bugs were fixed.

Devel::Profile is a Perl module to tell me why my perl program runs so slowly.

SYNOPSIS

perl -d:Profile program.pl
less prof.out

The Devel::Profile 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.
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:

perl -d:Profile test.pl

When the script terminates (or periodicly while running, see ENVIRONMENT) the profiler will dump the profile information to a file called prof.out. This file is human-readable, no additional tool is required to read it.

Note: Statistics are kept per sub, not per line.

Params::Profile is a Perl module for registering Parameter profiles.

SYNOPSIS

package Foo::Bar;

use Params::Profile;

### Single profile
Params::Profile->register_profile(
method => subroto,
profile => {
testkey1 => { required => 1 },
testkey2 => {
required => 1,
allow => qr/^d+$/,
},
testkey3 => {
allow => qr/^w+$/,
},
},
);

sub subroto {
my (%params) = @_;

return unlesss Params::Profile->validate(params => %params);
### DO SOME STUFF HERE ...
}

my $profile = Params::Profile->get_profile(method => subroto);

### Multiple Profile
Params::Profile->register_profile(
method => subalso,
profile => [
subroto,
{
testkey4 => { required => 1 },
testkey5 => {
required => 1,
allow => qr/^d+$/,
},
testkey6 => {
allow => qr/^w+$/,
},
},
],
);


sub subalso {
my (%params) = @_;

### Checks parameters agains profile of subroto and above registered
### profile
return unlesss Params::Profile->validate(params => %params);

### DO SOME STUFF HERE ...
}

Params::Profile provides a mechanism for a centralised Params::Check or a Data::FormValidater profile. You can bind a profile to a class::subroutine, then, when you are in a subroutine you can simply call Params::Profile->check($params) of Params::Profile->validate($params) to validate against this profile. Validate will return true or false on successfull or failed validation. Check will return what Data::FormValidator or Params::Check would return. (For Params::Check this is simply a hash with the validated parameters , for Data::FormValidator, this is a Data::FormValidator::Results object)

XUP is an attempt to replace static per-site user accounts, which most present dynamic web sites use in absence of an easy to use and open/shared user account system. It allows people to use a single account or profile with many sites, or one of their existing user profiles on multiple other web sites.

It is best suited to so called "community" sites, where the account serves mainly for lax identification of people among each other. It does not stipulate strong authentication (while OpenID or LID can be used) and is therefore only useful for applications with mediocre security and privacy demands.

Chat and discussion sites are the main target, but profiles in different applications can often also be enriched with them. They are meant to get used secondarily (as alternative) to static/local user accounts.

The XML format of user profiles is extremely simple, as is the associated login service API. Both are outlined and explained in the introduction (HTML). The format is basically an XMLified vCard with a few additions targetted at online/web communities. It is easy to parse and generate and therefore also suitable for profile exchange or import.

Theres also a more authoritative RFC-style text version of the current proposal, which provides further hints and explanations for implementors. Future extensions will get listed in the project Wiki however (field names in the XUP format are not regulated).

This effort is quite new, and therefore only very few actual (real-world) implementations are known so far.

Some software, like discussion boards (which mostly suffer from spaghetti code), are of course hard to extent with XML User Profiles. Even those that abstract their internal user database and UI logic reasonably well can often be difficult to adapt. It is however expected that the more professional systems will sooner than later be XUP compatible.

]project-open[ software is an open-source based project management system.
Functionality include internet collaboration and e-Rooms, discussion forums, Internet filestorage, customer management (CRM), timesheet management, management accounting with profit & loss per project, basic human resources management (HR), provider & freelance database, search engine, reporting, translation workflow and many more. We are currently working on four different "vertical solutions".
]project-open[ is a very complete online platform and already contains today many of the feature that are currently announced by many large international companies.
We can provide these features thanks to the open-source nature of ]project-open[ that allows us to tap into thousands of manyears of development time from other open-source projects such as OpenACS, AOLServer, PostgreSQL, CygWin, CVS, Postfix, Linux, Pound, Inno Setup, etc.
Additional modules: Data Warehouse, Room Reservation, e-Commerce, Automatic Testing, Content Management, Events, Bug Tracker, Categorysation, Wiki, RSS Support, Blog, WebDAV, Soap & XML-RPC, Calendar, Performance Profiling, CRM Campaigns, Jabber Integration, Filestorage, Glossary Database, News Aggregator, Online Surveys, Webmail.
]project-open[ is useful for project-oriented companies such as IT consultancies, general consultancies, advertizing agencies, etc. It is not very suitable for companies dealing with physical goods, because it doesnt contain the necessary modules (yet). Checkout Compiere or Open for Business as alternatives.
Enhancements:
- More than a dozen new modules and features have been included, including a round-trip integration with GanttProject, resource planning and resource assignments, GUI improvements, a new calendar module to show tasks and deadlines, a new bug tracker module, a new expenses and travel costs module, a new reporting engine, a new Petri-Net workflow engine with a graphical editor, project templates, and a new "configuration wizard" for automatic system configuration.

YourKit Java Profiler is a CPU and memory profiler that makes it easy to solve wide range of CPU- and memory-related performance problems.
YourKit Java Profiler features automatic leak detection, powerful tools for the analysis of memory distribution, an object heap browser, comprehensive memory tests as part of your JUnit testing process, extremely low profiling overhead, transparent deobfu
YourKit, LLC is a new technology leader, creator of the most innovative and intelligent tool for profiling Java applications. The YourKit Java Profiler has been already recognized by the IT professionals and analysts as the best profiling tool for Java.
With YourKit Java Profiler, both CPU and memory profiling have come to the highest professional level, where one can profile even huge applications with maximum productivity and zero overhead.
There are several, recent innovations to profiling that have gained well-deserved popularity among professional Java developers, both in big and small companies.
YourKit Java Profiler is a new leap in the evolution of profiling tools!
Main features:
General:
- On demand profiling
- Easiest installation and configuration
- Unlimited profiling for one fee
- Full, complete J2EE support
- Ability to profile in production environment
- Full Java 5.0 support
- Rich multiplatform support
- Robust profiler API
- IDE integration
- Filters in CPU and memory views
- Customizable user interface
- Easy way to connect to locally running applications
- Ability to export profiling results to HTML
- Remote profiling
CPU profiling:
- Two methods of CPU profiling: sampling and tracing
- CPU hot spots and method invocation trees
- Unique "Merged callees" view
- Method back traces view
- "Thread" and "wall" times
- Method "own time", that excludes time spent in called methods
- General snapshot info and deobfuscator configuration
Memory profiling:
- Unique comprehensive Objects view
- Easy way to browse instances of particular class
- "Find Paths" helps to find reasons of memory leaks
- Find strings that match given pattern
- Optional recording of object allocations
- "Quick Info" action
- Ability to compare memory snapshots
- Unique descriptive language for memory analysis
- General snapshot info and deobfuscator configuration
- Automated comprehensive memory test
Enhancements:
- Minor UI bug was fixed in "Merged Paths" view
- JRockit 5 R27.2 supported

HPCToolkit is an open-source suite of multi-platform tools for profile-based performance analysis of applications. The figure provides an overview of the toolkit components and their relationships.
Main features:
- hpcrun: a tool for profiling executions of unmodified application binaries using statistical sampling of hardware performance counters.
- hpcprof & xprof: tools for interpeting sample-based execution profiles and relating them back to program source lines.
- bloop: a tool for analyzing application binaries to recover program structure; namely, to identify where loops are present and what program source lines they contain.
- hpcview: a tool for correlating program structure information, multiple sample-based performance profiles, and program source code to produce a performance database.
- hpcviewer: a java-based GUI for exploring databases consisting of performance information correlated with program source.
A program called hpcview is at the toolkits center. It takes performance profiles, program structure information, and, under the direction of a configuration file, correlates it with application source code to produce a browsable performance database.
hpcview also enables the user to define expressions to compute derived metrics as functions other metrics already defined (e.g. measured metrics read from data files or previously-computed derived metrics).
Performance databases are explored using our Java-based hpcviewer user interface that enables one to explore an applications performance data in a top-down fashion and enables one to easily navigate back and forth between performance data and source code.
The user interface presents performance data in a hierarchical display. At any time, you are looking at some program context (program, file, procedure, loop, or line). Also displayed is the data for both the parent and the children of the current context. Up and down arrows on the lines of the display are used to walk the hierarchy.
In order to speed up top-down analysis, the interface also provides `flatten and `un-flatten buttons. Their icons hint at their function. `Flatten modifies the hierarchy by eliding non-leaf children of the current node and replacing them with the grandchildren.
Unflatten reverses this. Since the tables are sorted, the flatten operation makes short work of diving into the program from the top to identify the most important files, procedures, loops and statements.
Performance data manipulated by hpcview can come from any source, as long as the profile data can be translated or saved directly to a standard, profile-like input format. To date, the principal sources of input data for hpcview have been hardware performance counter profiles.
Such profiles are generated by setting up a hardware counter to monitor events of interest (e.g., primary cache misses), to generate a trap when the counter overflows, and then to histogram the program counter values at which these traps occur. For Linux, we developed the hpcrun tool to collect profiles by sampling hardware performance counters.
This tool uses UTKs PAPI library for access to hardware performance counters. A second tool, hpcprof is used to map profiles collected using hpcrun back to program source lines. hpcprof is based on code from Curt Janssens cprof/vprof profiler. On operating systems other than Linux, we use vendor-supplied tools to collect profile data. On MIPS+Irix platforms, we use SGIs ssrun tool to collect profiles. On Alpha+Tru64, we use either with Compaqs uprofile or DCPI utilities for this purpose.
hpcview and hpcviewer can be used to view profile-like data of any type, not just data sampled from hardware performance counters. To analyze one program that contained many register spills, we built a perl script to examine assembly code generated by the SGI compilers for MIPS+Irix and create profiles that map register spills back to source code lines.
To facilitate automation, the programs in HPCToolkit are intended to be run using scripts and configuration files. Once these are set up, rerunning the program to collect new data, and all of the steps that go into generating a browsable dataset can be completely automated. The scripts automate the collection of data and conversion of profile data into a common, XML-based format.
Other performance tools (e.g. SGIs ssrun) report performance data at the line, procedure, and program level. However, since much of the time in scientific programs is spent in loops; having data at the loop level as well is critical to facilitate performance tuning.
For this reason, HPCToolkit includes a binary analyzer bloop that extracts loop nesting structure from application binaries and uses symbol table line map information to map this structure back to the source programs level. Because bloop works on binaries, this process is independent of the language used (though in practice it can be somewhat compiler dependent).
The loop nesting structure information produced by bloop enables hpcview to associate performance data with each loop in a program without incurring any additional overhead for data collection during program execution.
Supported platforms: Pentium+Linux, Opteron+Linux, Athlon+Linux, Itanium+Linux, Alpha+Tru64 and MIPS+Irix.
HPCToolkit is open-source software released with a BSD-like license.