Home
collective.contentgenerator (0.2)
- collective.contentgenerator download link: http://plone.org/products/collective.contentgenerator/releases
- Homepage of collective.contentgenerator: http://plone.org/products/collective.contentgenerator
- collective.contentgenerator repository: http://svn.plone.org/svn/collective/collective.contentgenerator/
- Description source: http://svn.plone.org/svn/collective/collective.contentgenerator/trunk/collective.contentgenerator/README.txt
Overview
This package creates populated plone sites using dummy content and users. A likely partner package to the buildouts in collective.loadtesting which use funkload for functional and load testing of plone sites.
Ideally we want an egg that generates content as close to realworld sites as possible, for testing against. Whilst keeping them consistent per profile.
The starting point is to have an egg that installs a set of two profiles. Intranet and public website. These profiles can be adjusted for specific testing purposes, but by keeping a minimal set of base standards the benefit is that relative testing between code sets becomes more achievable.
The hope is that this can serve three user code testing bases ... core plone developers, third party developers and end users with sites for which performance is an issue.
Consistent content profiles should also serve the use of buildbot load testing comparisons over long timescales / code versions for unreal empty plone and these two more realworld profiles.
It was felt that a model of crawling out newsfeed content with tags, links, real sentences and language etc. is more realistic than some bulk plain latin text generator like lorem ipsum. Similarly users and groups are generated with proper names, rather than the user1-100 approach. Although highly consistent generated text has its place for load testing specific parts of plone such as the catalog. Well controlled harvested text can serve this purpose just as well and present a more realistic testing target.
NB: The RSS content source paradigm makes catering for delivery of content profiles with a large percentage of image or file content, as part of the same process, and it could also be adapted to point to foreign language feeds etc.
Currently large images are used for the addition of blobs to the database ... a common profile for intranets where a large number of bespoke file formats may be uploaded. Clearly this and a number of other performance issues can be dealt with by the employment of the correct add ons to remove blobs from the zodb, cache the interface etc. However the aim of this egg is to generate the content by default means. As a user of the egg you can then get relative quantitative data on the performance difference for the same content profile when applying any, or all of these techniques.
