Auto-pilot includes a simple language to control benchmark execution;
extensible file system benchmarking scripts as an example of how to use
Auto-pilot; automated and modular analysis tools called Getstats; and
automated graphing tool called Graphit that uses Gnuplot as a backend; and a
68-page user manual. Auto-pilot's configuration language includes support for
checkpoints, which allow you to reboot and resume the machine between
benchmark iterations without any manual intervention. Getstats produces
tabular reports, CSV files for outside analysis, and can compare two samples
using hypothesis testing. Using linear regression, Getstats can automatically
find memory leaks or other problems that degrade performance over time.
We have successfully used Auto-pilot for over three years on twenty
different projects, and it has saved us countless hours and days of work.
# |
Name (click for home page) |
Program |
Period |
Current Location |
1 |
Charles P. Wright |
PhD |
May 2003 - May 2006 |
Partner, Senior Software Architect, Illumon (New York, NY) |
2 |
Aditya Kashyap |
MS |
Sep 2003 - Dec 2004 |
Director, Fixed Income Financing, Barclays (New York, NY) |
3 |
Devaki Kulkarni |
MS |
Sep 2003 - Dec 2004 |
Staff Engineer, Performance and Storage groups, VMware, Inc. (Palo Alto, CA) |
4 |
Miretskiy "Eugene" Yeugeniy |
MS |
May 2003 - Dec 2004 |
Software Engineer Google (New York, NY) |
5 |
Jeffrey R. Osborn |
BS/MS |
Jan 2001 - May 2003 |
Associate Director, Customer Intelligence, MRM//McCann (Birmingham, MI) |
6 |
Charles P. Wright |
BS (Honors) |
Dec 2001 - May 2003 |
Application Software Developer, Walleye Software (New York, NY) |