prof
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 7
PHP Profiler Class
PHP Profiler Class is a PHP code profiler to aid in performance optimisation. more>>
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
<<lessThe 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
Download (0.004MB)
Added: 2005-04-12 License: GPL (GNU General Public License) Price:
1661 downloads
Devel::Profile 1.04
Devel::Profile is a Perl module to tell me why my perl program runs so slowly. more>>
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.
<<lessSYNOPSIS
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.
Download (0.007MB)
Added: 2006-10-03 License: Perl Artistic License Price:
1116 downloads
DBI::ProfileData 1.58
DBI::ProfileData can manipulate DBI::ProfileDumper data dumps. more>>
DBI::ProfileData can manipulate DBI::ProfileDumper data dumps.
SYNOPSIS
The easiest way to use this module is through the dbiprof frontend (see dbiprof for details):
dbiprof --number 15 --sort count
This module can also be used to roll your own profile analysis:
# load data from dbi.prof
$prof = DBI::ProfileData->new(File => "dbi.prof");
# get a count of the records (unique paths) in the data set
$count = $prof->count();
# sort by longest overall time
$prof->sort(field => "longest");
# sort by longest overall time, least to greatest
$prof->sort(field => "longest", reverse => 1);
# exclude records with key2 eq disconnect
$prof->exclude(key2 => disconnect);
# exclude records with key1 matching /^UPDATE/i
$prof->exclude(key1 => qr/^UPDATE/i);
# remove all records except those where key1 matches /^SELECT/i
$prof->match(key1 => qr/^SELECT/i);
# produce a formatted report with the given number of items
$report = $prof->report(number => 10);
# clone the profile data set
$clone = $prof->clone();
# get access to hash of header values
$header = $prof->header();
# get access to sorted array of nodes
$nodes = $prof->nodes();
# format a single node in the same style as report()
$text = $prof->format($nodes->[0]);
# get access to Data hash in DBI::Profile format
$Data = $prof->Data();
<<lessSYNOPSIS
The easiest way to use this module is through the dbiprof frontend (see dbiprof for details):
dbiprof --number 15 --sort count
This module can also be used to roll your own profile analysis:
# load data from dbi.prof
$prof = DBI::ProfileData->new(File => "dbi.prof");
# get a count of the records (unique paths) in the data set
$count = $prof->count();
# sort by longest overall time
$prof->sort(field => "longest");
# sort by longest overall time, least to greatest
$prof->sort(field => "longest", reverse => 1);
# exclude records with key2 eq disconnect
$prof->exclude(key2 => disconnect);
# exclude records with key1 matching /^UPDATE/i
$prof->exclude(key1 => qr/^UPDATE/i);
# remove all records except those where key1 matches /^SELECT/i
$prof->match(key1 => qr/^SELECT/i);
# produce a formatted report with the given number of items
$report = $prof->report(number => 10);
# clone the profile data set
$clone = $prof->clone();
# get access to hash of header values
$header = $prof->header();
# get access to sorted array of nodes
$nodes = $prof->nodes();
# format a single node in the same style as report()
$text = $prof->format($nodes->[0]);
# get access to Data hash in DBI::Profile format
$Data = $prof->Data();
Download (0.48MB)
Added: 2007-08-09 License: Perl Artistic License Price:
806 downloads
Performance Application Programming Interface 3.9.0
Performance Application Programming Interface is an API for a CPU performance counter. more>>
PAPI aims to provide the tool designer and application engineer with a consistent interface and methodology for use of the performance counter hardware found in most major microprocessors.
PAPI enables software engineers to see, in near real time, the relation between software performance and processor events.
The Performance API (PAPI) project specifies a standard application programming interface (API) for accessing hardware performance counters available on most modern microprocessors.
These counters exist as a small set of registers that count Events, occurrences of specific signals related to the processors function. Monitoring these events facilitates correlation between the structure of source/object code and the efficiency of the mapping of that code to the underlying architecture.
This correlation has a variety of uses in performance analysis including hand tuning, compiler optimization, debugging, benchmarking, monitoring and performance modeling. In addition, it is hoped that this information will prove useful in the development of new compilation technology as well as in steering architectural development towards alleviating commonly occurring bottlenecks in high performance computing.
PAPI provides two interfaces to the underlying counter hardware; a simple, high level interface for the acquisition of simple measurements and a fully programmable, low level interface directed towards users with more sophisticated needs.
The low level PAPI interface deals with hardware events in groups called EventSets. EventSets reflect how the counters are most frequently used, such as taking simultaneous measurements of different hardware events and relating them to one another.
For example, relating cycles to memory references or flops to level 1 cache misses can indicate poor locality and memory management. In addition, EventSets allow a highly efficient implementation which translates to more detailed and accurate measurements.
EventSets are fully programmable and have features such as guaranteed thread safety, writing of counter values, multiplexing and notification on threshold crossing, as well as processor specific features. The high level interface simply provides the ability to start, stop and read specific events, one at a time.
PAPI provides portability across different platforms. It uses the same routines with similar argument lists to control and access the counters for every architecture. As part of PAPI, we have predefined a set of events that we feel represents the lowest common denominator of every good counter implementation.
Our intent is that the same source code will count similar and possibly comparable events when run on different platforms. If the programmer chooses to use this set of standardized events, then the source code need not be changed and only a fresh compilation and link is necessary. However, should the developer wish to access machine specific events, the low level API provides access to all available events and counting modes.
If an event or feature does not exist on the current platform, PAPI returns an appropriate error code. This significantly reduces the porting effort of code using PAPI because the semantics of each call to PAPI remains the same, just the argument lists need updating. In addition to the standard set, each PAPI implementation supports all native events through the ability to directly accept platform specific counter numbers. Definitions for most, if not all of these, are included as conditional macros in the header file. In this way, PAPI avoids having inefficient code to translate all events for all platforms into a uniform representation and back again.
This translation is only done for the relatively few events defined in the standardized set. Some processors like those in the POWER series have counter groups. They enable access to specific groups of counters, instead of individual events. This presents a serious portability problem, thus PAPI abstracts hardware counters from their groups with a packed naming scheme. Each counter control value or event is made up of the counter group number and the number of the specific counter in that group.
PAPI can be divided into two layers of software. The upper layer consists of the API and machine independent support functions. The lower layer defines and exports a machine independent interface to machine dependent functions and data structures. These functions access the substrate, which may consist of the operating system, a kernel extension or assembly functions to directly access the processors registers.
PAPI tries to use the most efficient and flexible of the three, depending on what is available. Naturally, the functionality of the upper layers heavily depends on that provided by the substrate. In cases where the substrates do not provide highly desirable features, PAPI attempts to emulate them as described below.
PAPI makes sure the underlying operating system or library guards against overflow of counter values.
Each counter can potentially be incremented multiple times in a single clock cycle. This combined with increasing clock speeds and the small precision of some of the physical counters means that overflow is likely to occur.
One of the more advanced features of PAPI is to provide a portable implementation of asynchronous notification when counters exceed a user specified value.
This functionality provides the basis for PAPIs SVR4 compatible profiling calls, that generate an accurate histogram of performance interrupts based on hardware metrics, not on time. Such functionality provides the basis for all line level performance analysis software, from the antiquated days of AT&Ts prof to SGIs SpeedShop. Thus for any architecture with even the most rudimentary access to hardware performance counters, PAPI provides the foundation for a truly portable, source level, performance analysis tool based on real processor statistics.
Enhancements:
- The API was extended to decouple abstraction layers from hardware support and to provide initial support for different types of performance counters.
<<lessPAPI enables software engineers to see, in near real time, the relation between software performance and processor events.
The Performance API (PAPI) project specifies a standard application programming interface (API) for accessing hardware performance counters available on most modern microprocessors.
These counters exist as a small set of registers that count Events, occurrences of specific signals related to the processors function. Monitoring these events facilitates correlation between the structure of source/object code and the efficiency of the mapping of that code to the underlying architecture.
This correlation has a variety of uses in performance analysis including hand tuning, compiler optimization, debugging, benchmarking, monitoring and performance modeling. In addition, it is hoped that this information will prove useful in the development of new compilation technology as well as in steering architectural development towards alleviating commonly occurring bottlenecks in high performance computing.
PAPI provides two interfaces to the underlying counter hardware; a simple, high level interface for the acquisition of simple measurements and a fully programmable, low level interface directed towards users with more sophisticated needs.
The low level PAPI interface deals with hardware events in groups called EventSets. EventSets reflect how the counters are most frequently used, such as taking simultaneous measurements of different hardware events and relating them to one another.
For example, relating cycles to memory references or flops to level 1 cache misses can indicate poor locality and memory management. In addition, EventSets allow a highly efficient implementation which translates to more detailed and accurate measurements.
EventSets are fully programmable and have features such as guaranteed thread safety, writing of counter values, multiplexing and notification on threshold crossing, as well as processor specific features. The high level interface simply provides the ability to start, stop and read specific events, one at a time.
PAPI provides portability across different platforms. It uses the same routines with similar argument lists to control and access the counters for every architecture. As part of PAPI, we have predefined a set of events that we feel represents the lowest common denominator of every good counter implementation.
Our intent is that the same source code will count similar and possibly comparable events when run on different platforms. If the programmer chooses to use this set of standardized events, then the source code need not be changed and only a fresh compilation and link is necessary. However, should the developer wish to access machine specific events, the low level API provides access to all available events and counting modes.
If an event or feature does not exist on the current platform, PAPI returns an appropriate error code. This significantly reduces the porting effort of code using PAPI because the semantics of each call to PAPI remains the same, just the argument lists need updating. In addition to the standard set, each PAPI implementation supports all native events through the ability to directly accept platform specific counter numbers. Definitions for most, if not all of these, are included as conditional macros in the header file. In this way, PAPI avoids having inefficient code to translate all events for all platforms into a uniform representation and back again.
This translation is only done for the relatively few events defined in the standardized set. Some processors like those in the POWER series have counter groups. They enable access to specific groups of counters, instead of individual events. This presents a serious portability problem, thus PAPI abstracts hardware counters from their groups with a packed naming scheme. Each counter control value or event is made up of the counter group number and the number of the specific counter in that group.
PAPI can be divided into two layers of software. The upper layer consists of the API and machine independent support functions. The lower layer defines and exports a machine independent interface to machine dependent functions and data structures. These functions access the substrate, which may consist of the operating system, a kernel extension or assembly functions to directly access the processors registers.
PAPI tries to use the most efficient and flexible of the three, depending on what is available. Naturally, the functionality of the upper layers heavily depends on that provided by the substrate. In cases where the substrates do not provide highly desirable features, PAPI attempts to emulate them as described below.
PAPI makes sure the underlying operating system or library guards against overflow of counter values.
Each counter can potentially be incremented multiple times in a single clock cycle. This combined with increasing clock speeds and the small precision of some of the physical counters means that overflow is likely to occur.
One of the more advanced features of PAPI is to provide a portable implementation of asynchronous notification when counters exceed a user specified value.
This functionality provides the basis for PAPIs SVR4 compatible profiling calls, that generate an accurate histogram of performance interrupts based on hardware metrics, not on time. Such functionality provides the basis for all line level performance analysis software, from the antiquated days of AT&Ts prof to SGIs SpeedShop. Thus for any architecture with even the most rudimentary access to hardware performance counters, PAPI provides the foundation for a truly portable, source level, performance analysis tool based on real processor statistics.
Enhancements:
- The API was extended to decouple abstraction layers from hardware support and to provide initial support for different types of performance counters.
Download (2.9MB)
Added: 2007-04-23 License: BSD License Price:
925 downloads
Coursor 1.0
Coursor project is a Web application for academic environments. more>>
Coursor project is a Web application for academic environments.
Coursor is a Web-based academic course system for assigning students to university courses.
It has an evolutionary algorithm for assigning students to the courses they requested. This algorithm tries to find an optimal distribution of students to existing courses while taking their preferences into account.
The system supports multiple roles for users: Admin, Student, Teacher/Prof, or Tutor.
A user can also have multiple roles.
It supports international localization, currently in English, German, French, Russian, and Arabic
Main features:
- Browser independent usage for students, teachers and admins alike (no frames, no necessary JavaScript, no cookies).
- Platform independent (entirely written in JAVA).
- Runs on APACHE Tomcat and uses a Postgresql Database.
- Evolutionary Algorithm to assign students to courses.
- Multiple Roles: Administrator, Teacher/Prof, Tutor and Student. One person can have multiple roles.
Enhancements:
- Encoding for Russian fixed
- PropertyEditor (propEdit.sf.net) programmed, will be released as own package. Eases Tranlation a lot.
- I18N target in build.xml starts PropertyEditor
- Serializable classes with ID (Eclipse wanted that)
<<lessCoursor is a Web-based academic course system for assigning students to university courses.
It has an evolutionary algorithm for assigning students to the courses they requested. This algorithm tries to find an optimal distribution of students to existing courses while taking their preferences into account.
The system supports multiple roles for users: Admin, Student, Teacher/Prof, or Tutor.
A user can also have multiple roles.
It supports international localization, currently in English, German, French, Russian, and Arabic
Main features:
- Browser independent usage for students, teachers and admins alike (no frames, no necessary JavaScript, no cookies).
- Platform independent (entirely written in JAVA).
- Runs on APACHE Tomcat and uses a Postgresql Database.
- Evolutionary Algorithm to assign students to courses.
- Multiple Roles: Administrator, Teacher/Prof, Tutor and Student. One person can have multiple roles.
Enhancements:
- Encoding for Russian fixed
- PropertyEditor (propEdit.sf.net) programmed, will be released as own package. Eases Tranlation a lot.
- I18N target in build.xml starts PropertyEditor
- Serializable classes with ID (Eclipse wanted that)
Download (1.5MB)
Added: 2006-10-19 License: GPL (GNU General Public License) Price:
1105 downloads
SLMotion 1.2
SLMotion is a small prog for a small request. more>>
SLMotion is a small prog for a small request. Ive to make a film with a special effect : slow a video and speed up after ... like prof films. I search a tool and dont find one on Linux, so i make it myself.
To run :
Untar the archive
./slmotion
Usage :
1 - Load a video
2 - Select a part of the video to apply effect. Take most frame that you need its more easy to reimplement your video after.
3 - Select precisely the first and last image to apply the effect
4 - Choose the value to reduce speed
5 - Lets go and enjoy
<<lessTo run :
Untar the archive
./slmotion
Usage :
1 - Load a video
2 - Select a part of the video to apply effect. Take most frame that you need its more easy to reimplement your video after.
3 - Select precisely the first and last image to apply the effect
4 - Choose the value to reduce speed
5 - Lets go and enjoy
Download (0.14MB)
Added: 2006-09-19 License: GPL (GNU General Public License) Price:
1132 downloads
Web Interface for SIP Trace 0.4
Web Interface for SIP Trace is a PHP Web Interface that permits you to connect on a remote host/port and listen/filter. more>>
Web Interface for SIP Trace is a PHP Web Interface that permits you to connect on a remote host/port and listen/filter.
Web Interface for SIP Trace was born as a prof concept of the idea to capture SIP traffic from a remote host (SIP Proxy, Gateway, etc) and show up alive SIP messages about an specific dialog (filtered by From SIP user) to help our tech support team to debug SIP transactions in a friendly way.
There are 3 peaces of software in this process, 2 of them was created by us:
1. ngrep: Created by Jordan Ritter - http://ngrep.sourceforge.net
ngrep strives to provide most of GNU greps common features, applying them to the network layer. ngrep is a pcap-aware tool that will allow you to specify extended regular or hexadecimal expressions to match against data payloads of packets. It currently recognizes TCP, UDP and ICMP across Ethernet, PPP, SLIP, FDDI, Token Ring and null interfaces, and understands bpf filter logic in the same fashion as more common packet sniffing tools, such as tcpdump and snoop.
2. siptraced: Created by Devel-IT - http://www.devel.it
siptraced is a perl daemon who reads a ngrep log file and push each line on a TCP port, so every one connected on this port will listen all traffic captured by ngrep (dangerous and perhaps a waste of bandwidth). There is no user/IP authentication yet.
3. WIST: Created by Devel-IT - http://www.devel.it
WIST is a PHP Web Interface who permits you to connect on a remote host/port and listen/filter a SIP dialog of an specific SIP From number, avoiding to listen all captured traffic pushed by siptraced. The STOP control is done by browsers stop button. The output is colorized and "Call-ID" tag is highlighted to make it simple to be located. You can run WIST on any host running a Web Server with PHP >= 4.0.x and authorized to connect on siptraced remote TCP port.
There is no guarantee about our softwares, use it by your own risk. Read the source code first, if you didnt understand it dont use it!
Enhancements:
- Minor bugfixes.
- Shows error messages formatted in red.
<<lessWeb Interface for SIP Trace was born as a prof concept of the idea to capture SIP traffic from a remote host (SIP Proxy, Gateway, etc) and show up alive SIP messages about an specific dialog (filtered by From SIP user) to help our tech support team to debug SIP transactions in a friendly way.
There are 3 peaces of software in this process, 2 of them was created by us:
1. ngrep: Created by Jordan Ritter - http://ngrep.sourceforge.net
ngrep strives to provide most of GNU greps common features, applying them to the network layer. ngrep is a pcap-aware tool that will allow you to specify extended regular or hexadecimal expressions to match against data payloads of packets. It currently recognizes TCP, UDP and ICMP across Ethernet, PPP, SLIP, FDDI, Token Ring and null interfaces, and understands bpf filter logic in the same fashion as more common packet sniffing tools, such as tcpdump and snoop.
2. siptraced: Created by Devel-IT - http://www.devel.it
siptraced is a perl daemon who reads a ngrep log file and push each line on a TCP port, so every one connected on this port will listen all traffic captured by ngrep (dangerous and perhaps a waste of bandwidth). There is no user/IP authentication yet.
3. WIST: Created by Devel-IT - http://www.devel.it
WIST is a PHP Web Interface who permits you to connect on a remote host/port and listen/filter a SIP dialog of an specific SIP From number, avoiding to listen all captured traffic pushed by siptraced. The STOP control is done by browsers stop button. The output is colorized and "Call-ID" tag is highlighted to make it simple to be located. You can run WIST on any host running a Web Server with PHP >= 4.0.x and authorized to connect on siptraced remote TCP port.
There is no guarantee about our softwares, use it by your own risk. Read the source code first, if you didnt understand it dont use it!
Enhancements:
- Minor bugfixes.
- Shows error messages formatted in red.
Download (0.023MB)
Added: 2006-03-30 License: GPL (GNU General Public License) Price:
1312 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above prof search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
