Differences between revisions 2 and 3
Revision 2 as of 2011-04-07 18:14:47
Size: 2945
Editor: oss-staff
Comment:
Revision 3 as of 2011-04-10 20:31:42
Size: 2558
Editor: nat-broad-resnet-out-1
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
This should be ported to speed.python.org, where the tests will run on various implementations of python to compare performance across all of them. This should be ported to speed.python.
Line 9: Line 9:
When all of the tests are ported, a website needs to be created that will run all the tests using different interpeters, and display the results. This will most likely be done with [[http://wiki.github.com/tobami/codespeed/|codespeed]]. Unlike the the pypy site, however, speed.python.org will need to show benchmarks from many different implementations of python, and be constructed in a way that makes it easy to add new implementations later on. When all of the tests are ported, a website needs to be created that will run all the tests, and display the results. This will most likely be done with [[http://wiki.github.com/tobami/codespeed/|codespeed]].
Line 22: Line 22:
At the end of the summer, a website speed.python.org should exist, that runs the benchmarks and profilers from speed.pypy.org on various implementations of python. At the end of the summer, a website speed.python.org should exist, that runs the benchmarks and profilers from speed.pypy.org.

Speed.Python.Org

Speed.Python.Org is a Google Summer of Code 2011 Proposal by Jarek Sedlacek.

PyPy currently has benchmarks and profiling available at speed.pypy.org. This should be ported to speed.python.

The first goal is to port all of the tests to Python 3.

When all of the tests are ported, a website needs to be created that will run all the tests, and display the results. This will most likely be done with codespeed.

Milestones

Start of Program (May 24) The first task that will be addressed during the project is porting the tests to python 3. The only thing that needs to be done to prepare for this is to have a version control repository set up.

Midterm Evaluation (July 12) By the mid point of the project, the majority of the tests should be ported to python 3. Ideally they all will be, but some with extenuating circumstances (dependencies on large frameworks like django that are not yet ported to python3, for example) may be impossible to port over the summer.

Final Evaluation (Aug 16) At the end of the summer, a website speed.python.org should exist, that runs the benchmarks and profilers from speed.pypy.org.

About Me

I'm a currently a student at Rutgers University, studying Physics and Computer Science. I work for Open Systems Solutions at Rutgers, where I work as a member of a team responsible for building and maintaining the RPM packages used through a user community of 70,000 faculty, staff, and students. I also created projects for use at the university, like SpamAssassin plugins for detecting spam in foreign languages, and a python program to use Cacti thresholds as Nagios plugins.

I've also spent a summer working for the United States Army Armament Research Development And Engineering Center (ARDEC). I designed and implemented a multi-threaded graphical application in C++ for the Small Arms Deployable Sensor Network (SmADSNet), including:

  • an interface in QT for users to visualize information from a mesh network of sensor nodes overlaid on satellite imagery
  • a network stack enabling TCP, UDP and serial communication with a mesh network
  • MySQL database backend with export ability for post-analysis and the ability to sync from multiple sources

Contact Info

Name: Jarek Sedlacek

Email: JarekSedlacek@gmail.com

Phone: 973-229-8333

XMPP: jarek@rutgers.edu

Address:

  • 29 Lakeshore Dr. Rockaway, NJ 07866 United State of America

SummerOfCode/SpeedDotPythonDotOrg (last edited 2012-06-12 18:36:49 by techtonik)

Unable to edit the page? See the FrontPage for instructions.