Free mysql benchmark suite software for linux

Easy Benchmarking Suite is aimed at testing and benchmarking sites. Basically, the suite can:
- Issue requests to a URL. A benchmark typically consists of a given number of clients that concurrently issue a number of requests. A request can be any HTTP request (GET, POST, HEAD etc.) with all necessary HTTP header information (session cookies, basic authentication information, etc.);
- Get a quick overview of the results of a benchmark: how many trials succeeded, what are the average times for connecting and processing, what is the standard deviation of these times;
- Prepare a GnuPlot command file so that the obtained results can be plotted.
This document describes the suite. Furthermore, manual pages are provided for the separate parts of the suite: sitebench, sitecollect, and siteplot.

The Bioinformatics Benchmark System is an attempt to build a reasonable testing framework, tests, and data, to enable end users and vendors to probe the performance of their systems.

What we are trying to do is to create a framework for testing, and a core set of tests that all may download and use to probe specific elements of systems performance.

Moreover, the source to these tests are available under GPL, and are hosted on Bioinformatics.org and Scalable Informatics LLC The idea is to enable end users, consumers, systems developers, and others to easily build and use meaningful tests for measurement and tuning reasons.

Joe Landman from Scalable Informatics LLC conceived the idea and wrote the original codes. We are looking for additional benchmark code suggestions, tests, data sets, etc.

Current baseline tests are several NCBI BLAST runs, several HMMer runs, and a variety of others. We plan to include ClustalW, X!Tandem, various chemistry, dynamics, and related tests, as well as several others.

Tests such as LINPACK or HPL simply do not provide meaningful performance indicators or predictive models for high performance informatics. Unfortunately, nor do a number of more recent and focused tests.

This is a problem as LINPACK and HPL specifically test the performance on various matrix operations, where you have effectively regular memory access patterns, and specific mathematical operations.

These codes are most useful for comparison to codes with heavy floating point operations, and interleaved memory traffic. These codes were not designed for comprehensive systems benchmarking, where disk I/O, memory latency, and other factors all contribute to the performance issues.

The best tests are the ones that are most similar to the codes you will run on the machine. The tests themselves should be reasonable approximations to a real execution of your code, using real data. You may need to pare it back in order to get realistic run times.

You should have a reasonable subset of data sizes. A single test does not tell you how your system scales, and one of the reasons for the existance of this test is specifically to allow you to test the performance while you increase various aspects of the workload.

You rarely get a quiescent system in a cluster, so we would recommend that you try to run in as realistic an operating environment as possible. A baseline in a quiescent system is fine, but it may set your expectations unreasonably.
top

Benchmark is a Perl module with benchmark running times of Perl code.

SYNOPSIS

use Benchmark qw(:all) ;

timethis ($count, "code");

# Use Perl code in strings...
timethese($count, {
Name1 => ...code1...,
Name2 => ...code2...,
});

# ... or use subroutine references.
timethese($count, {
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
});

# cmpthese can be used both ways as well
cmpthese($count, {
Name1 => ...code1...,
Name2 => ...code2...,
});

cmpthese($count, {
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
});

# ...or in two stages
$results = timethese($count,
{
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
},
none
);
cmpthese( $results ) ;

$t = timeit($count, ...other code...)
print "$count loops of other code took:",timestr($t),"n";

$t = countit($time, ...other code...)
$count = $t->iters ;
print "$count loops of other code took:",timestr($t),"n";

# enable hires wallclock timing if possible
use Benchmark :hireswallclock;

The Benchmark module encapsulates a number of routines to help you figure out how long it takes to execute some code.

timethis - run a chunk of code several times
timethese - run several chunks of code several times
cmpthese - print results of timethese as a comparison chart
timeit - run a chunk of code and see how long it goes
countit - see how many times a chunk of code runs in a given time

MySQL table patcher is a patch that reads table creation file (tables.sql) and compares it to what mysqldump gives. It creates SQL clauses to update the database to match the creation file.

Cache::Benchmark is a Perl module that tests the quality and speed of a cache module to compare cachemodules and algorithms.

SYNOPSIS

use Cache::Benchmark();
use Cache::MemoryCache();
use Cache::SizeAwareMemoryCache();

my $cache_1 = new Cache::MemoryCache({
namespace => my,
default_expires_in => 1,
});
my $cache_2 = new Cache::SizeAwareMemoryCache({
namespace => my,
default_expires_in => 1,
max_size => 400,
});

my $test = new Cache::Benchmark();
$test->init( access_counter => 10_000 );

$test->run($cache_1);
print $test->get_printable_result();

$test->run($cache_2);
print $test->get_printable_result();

Gtk+ MySQL Command Center is a GUI client for MySQL databases.
Gtk+ MySQL Command Center will help you to use your MySQL servers, do requests on them, manage their configuration (users, process, etc.), dump datas and structure and more.
You dont need GNOME to use it.
Main features:
- Use gtk+ only (doesnt need Gnome)
- Manage a mysql server list (Store in a XML file)
- SQL Query window (with query duplication capabilities)
- Edit value directly in the results table
- Multi-window system ... not all request in the same window
- Dump SQL table|database|serveur|request into SQL, XML and CSV files

Asterisk Manager Suite (AMS) is a collection of software; an abstraction library called Asterisk Manager Interface (AMI), a proxy daemon called Asterisk Manager Proxy (AMP), and a gui client interface called Asterisk Manager Administrator (AMA).
The intention of the software is to make management and administration of the Asterisk Open Source PBX easier. The software is currently targetted at corporate environments with call centers but plans for further expansion exist.
The C library, libami (AMI) is intended to make executing commands through Asterisks Manager Interface easier. The library is used extensively in both AMP and AMA, although you could use it in your own software as well.
The proxy daemon is intended to remedy an outstanding issue with Asterisks Manager Interface: The interface does not deal well with excessive connections. To get around this, a proxy is a suitable solution. As well as simply being a proxy, AMP has other functions as well, including recording statistics and activities of call center agents.
AMA is intended to be a gtk application for monitoring and administrating an Asterisk server. AMA requires AMP for connectivity and has many functions as well as some planned in the future. AMA was first inspired by Asterisks own gastman client, which was well done, but to small to be of any real use to anyone in a corporate environment except perhaps admins.
Enhancements:
- Minor bugfixes dealing with ampd not sending events properly.

MySQL Abstractor package contains PHP classes that implements a MySQL database abstraction layer.

It provides several classes. There is one for establishing connections and executing SQL queries, another for composing and executing SELECT, INSERT, UPDATE and DELETE queries from a list of parameters, and a wrapper class to simplify the usage of the other two classes.