Bug #6219
Updated by Brett Smith almost 9 years ago
Short version: implement a separate test suite that reports timing profiles. Eventually we'll have comprehensive performance tests, but for this ticket, focus tests on operations that parse and manipulate collection objects and manifests. In particular, try to avoid talking to Keep:
* List the contents of a project that contains many collections
* List the contents of a large collection
* Update one collection by copying files from another
* (Assuming FUSE supports it) Create a collection from scratch by making a directory for it and copying files to it from an existing Collection, and saving
* (Others? But again, the focus is on collections performance.)
When in doubt, for implementation guidance, follow the pattern for the API server and Workbench established in #6087, unless that's grossly un-Pythonic. Use the large collection test fixtures created during that development.