Hi all, The UC Berkeley project team would like to make a performance improvement and contribute it back to the core system. We propose that this work result in a version 3.2.2 release of CollectionSpace. Your comments and suggestions regarding this proposal are welcomed. This minor release, following shortly after a similar minor release, version 3.2.1, would be focused on a single goal: improving the responsiveness of partial term matching in autocomplete fields. With very large numbers of terms, these matches can take longer than is desirable. When multiple users are on the system, the combined effect of these delays look like the system has frozen. This performance improvement work is described in this JIRA issue and its sub-tasks: http://issues.collectionspace.org/browse/CSPACE-5941 The project team is exploring a hand-tuned SQL query that offers some promise of significantly outperforming the query automatically generated by the Nuxeo content management system. We're now working on integrating that query into CollectionSpace Services layer code and testing the integration. If all goes well, version 3.2.2 is expected to be released by mid-April. That version would also include some other minor performance improvements and bugfixes that have come out since version 3.2.1. Those minor changes made to date are all currently listed on the wiki page for Release 3.3: http://wiki.collectionspace.org/display/collectionspace/Release+3.3 If there is a version 3.2.2 incorporating the partial term matching performance improvements and those other minor changes to date, the remaining, more extensive changes described on that page would still be targeted for Release 3.3. Thanks, Chris Hoffman and the UCB team

There's now a wiki page for this proposed version 3.2.2, as well: http://wiki.collectionspace.org/display/collectionspace/Release+3.2.2 On Wed, Apr 3, 2013 at 4:21 PM, Chris Hoffman <chris_h@berkeley.edu> wrote: > Hi all, > > The UC Berkeley project team would like to make a performance > improvement and contribute it back to the core system. We propose > that this work result in a version 3.2.2 release of CollectionSpace. > Your comments and suggestions regarding this proposal are welcomed. > > This minor release, following shortly after a similar minor release, > version 3.2.1, would be focused on a single goal: improving the > responsiveness of partial term matching in autocomplete fields. With > very large numbers of terms, these matches can take longer than is > desirable. When multiple users are on the system, the combined effect > of these delays look like the system has frozen. > > This performance improvement work is described in this JIRA issue > and its sub-tasks: > http://issues.collectionspace.org/browse/CSPACE-5941 > > The project team is exploring a hand-tuned SQL query that offers > some promise of significantly outperforming the query automatically > generated by the Nuxeo content management system. We're now working > on integrating that query into CollectionSpace Services layer code and > testing the integration. > > If all goes well, version 3.2.2 is expected to be released by > mid-April. That version would also include some other minor > performance improvements and bugfixes that have come out since version > 3.2.1. Those minor changes made to date are all currently listed on > the wiki page for Release 3.3: > > http://wiki.collectionspace.org/display/collectionspace/Release+3.3 > > If there is a version 3.2.2 incorporating the partial term matching > performance improvements and those other minor changes to date, the > remaining, more extensive changes described on that page would still > be targeted for Release 3.3. > > Thanks, > Chris Hoffman and the UCB team > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >