[pygr-notify] [pygr] r250 commited - Edited wiki page through web user interface.
codesite-noreply at google.com
codesite-noreply at google.com
Wed Jul 29 19:36:08 PDT 2009
Revision: 250
Author: marecki
Date: Wed Jul 29 19:35:36 2009
Log: Edited wiki page through web user interface.
http://code.google.com/p/pygr/source/detail?r=250
Modified:
/wiki/MegatestSetup.wiki
=======================================
--- /wiki/MegatestSetup.wiki Fri Jun 26 14:22:33 2009
+++ /wiki/MegatestSetup.wiki Wed Jul 29 19:35:36 2009
@@ -2,7 +2,9 @@
= Introduction =
-_Megatests_ is a special class of tests performed on Pygr code, whose aim
is to ensure adequate performance of Pygr under heavy load. Running such
tests is particularly important during active development of code, as it
allows one to quickly detect any changes negatively impacting performance;
on the other hand, they can also be used to benchmark Pygr performance or,
indirectly, observe performance-degrading system problems on a certain
machine or machines.
+_Megatests_ is a special class of tests performed on Pygr code, which
differ from regular tests in that they require significant amounts of input
data, disc space and/or CPU time. As such, they are not run automatically
by the test suite.
+
+The aim of most existing megatests is to ensure adequate performance of
Pygr under heavy load. Running such tests is particularly important during
active development of code, as it allows one to quickly detect any changes
negatively impacting performance; on the other hand, they can also be used
to benchmark Pygr performance or, indirectly, observe performance-degrading
system problems on a certain machine or machines.
The purpose of this page is to provide complete instructions for everyone
wishing to run megatests on his/her system - from obtaining the necessary
data through actual running of megatests to automatic periodic running and
reporting.
@@ -21,8 +23,6 @@
* Everything needed by Pygr itself;
- * [http://somethingaboutorange.com/mrl/projects/nose/ Nose] (megatests
haven't been rewritten for the new test framework yet);
-
* _(optional)_ A local worldbase XML-RPC server, so that the
data-download test is not affected by the quality of your connection to the
UCLA one;
* Sequence data, miscellaneous input and reference output used by
megatests; obtaining and installing these will be described below.
More information about the pygr-notify
mailing list