[Neo-report] Quick overview of reports on this list

Vincent Pelletier vincent at nexedi.com
Fri Feb 19 15:52:09 CET 2010


Hi.

A quick overview of automated tests sending reports to this list:

Unit & functional tests:
  Ex: "[Neo-report] Neo : 450 Tests, 30 Errors, 12 Failures"
  Provides an overview of known bugs or missing features.
  Due to the recent inclusion of many ZODB tests (comming straight from ZODB
  code and ran on a Neo storage) there are still many failures, reducing the
  number of failures is one of our highest priority.

Import performance tests:
  Ex: "[Neo-report] Neo : 1083.2 KB/s (  19.0 MB)"
  Provides an overviews of performances in write-intensive tasks.
  The test imports a FileStorage (Data.fs) into a Neo storage.
  There is a variety of imported FileStorages - whose sizes is displayed in
  mail subject - to get an idea of how different object patterns behave (many
  transactions often overwriting objects, transactions who never overwrite
  objects, transactions with small objects, ...).
  The past 2 weeks have seen a huge (factor of ~5) improvement, with
  little effort.
  There is currently no way to compare similar uses with Zeo storage, it will
  be added in the future.

Soon, a new kind of automated test will be added, which measures the 
scalability of Neo, by running import tests (just as above) of a single 
FileStorage on multiple successive Neo cluster configurations (1 node 0 
replica, 2 nodes 0 replica, 2 nodes 1 replica, ...) so our progress on this 
topic can be monitored.

Regards,
-- 
Vincent Pelletier



More information about the Neo-report mailing list