Revision as of 12:59, 11 April 2012

Development

Joseph tarted working on the office normalization not working, handed off to Austin: http://code.google.com/p/archivematica/issues/detail?id=961
- Issue 961:12.04 + DocumentConverter.py normalization failures. Joseph would like to give this high priority. There have been some major changes to unoconv, and he'd like to give it a shot again. It would be nice to fix

Issue 304: Transcoding with Open Office fails periodically.

Austin is trying to track some similar issue down.. but will post issues to libre office and launchpad as well

Multi-node processor testing: Joseph is not seeing database drops/disconnects in archivematica 0.9 dev on precise.
- He's holding back on testing till we get a better idea of what metrics we want to keep.
- There's a limit to how much can be tested in the office; the limit is the disk, so we will have to upgrade
- however, it sounds like our ciaus test environment is confirming thus far that our multi-node mysql drops problem has dissappeared after full 12.04 upgrades
- for testing, we should probably be comparing results for individual micro-services as well as total ingest-to-aip/dip creation times
- Austin will create the test net on openhosting, maybe in an afternoon/evening
Austin will take over the testing process & docs, he will speak to Joseph about all the variations to test for, e.g. specific micro-services vs total pipeline time, bulk set of sample data vs testing for specific format types
- All of the testing needs to be ordered in a systematic way, e.g. separate tests that keep everything the same except a change in one factor, ie. sample data, microservice, number of nodes
- After we have all those stats (hopefully with positive results, ie. adding more processors boosts performance) we can add distributed FS as a new test variable, eg CEPH
  - FS is a variable as well for the initial set of baseline tests - EXT4+nfs right now

@@ Line 22: / Line 22: @@
 **All of the testing needs to be ordered in a systematic way, e.g. separate tests that keep everything the same except a change in one factor, ie. sample data, microservice, number of nodes
 **After we have all those stats (hopefully with positive results, ie. adding more processors boosts performance) we can add distributed FS as a new test variable, eg CEPH
+***FS is a variable as well for the initial set of baseline tests - EXT4+nfs right now
 = Chat log =