The new rolling content views feature automatically redistributes repositories as they receive new content through syncs or uploads. This means that sync & upload tasks for repositories inside rolling content views trigger rolling content view "refresh" operations, which redistributes content in Pulp.

For one example for testing, we could see how sync & upload performance is affected by, say, 100 rolling content views all belonging to some repository. How might this also affect the use of the "auto sync to capsules" feature after CV promotion?

Also note that Library is the only environment currently supported to be used with rolling CVs. This means that capsule users will be required to sync Library to their capsules, which can be a performance issue.

Let me (iballou@redhat.com ) know if there are any questions about the use of rolling content views to help with this testing.