Está viendo la ayuda para la versión:

The default “Tough Day” test simulates the daily load of around 1000 authors in a worst-case scenario with all the operations going on at the same time. To make things worse the test deviates from best practices using very unfortunate, not recommended content structures.
Nota:
For information about maximizing response times, see Performance Optimization.
Tough Day has mainly two usecases:
- Stress testing the system with a much larger number of users in parallel than can normally occur
- Simulate a certain number of users in parallel that is close to the number of peak users an author installation can have. This is the more used test.
Precaución:
Please note that for the second use-case, the createPages.thinkt parameter needs to be specified. Example:
java -Xmx1024m -Dhostname=localhost -Dport=4502 -DcreatePages.toplevels=2 -DcreatePages.sublevels=2 -DcreatePages.subsublevels=2 -DcreatePages.concurrentUsers=3 -DcreatePages.rampup=1 -DcreatePages.thinkt=5 -DcreatePages.activate=true -DcreatePages.delete=true -jar toughday.jar createPages
Nota:
For estimating the number of users on an author instance, you can use the Request Analysis Script
A cron job triggers a bash script which downloads the current nightly build. The nightly build is uploaded with the S3CMD tools into an Amazon S3 bucket inside the cloud. Multiple EC2 machines with different configurations and hardware specifications are instantiated from existing AMIs. Each machine starts an ANT script which installs and configures the nightly build of CQ and starts all configured tests parallel. After the tests have passed or failed the results are gathered and send back to the Day QaBase. The virtual machines are terminated 48 hours later.
Creates content pages inside CQ, adds different components to the page, activates the page and deletes the page. This test is executed with 30 concurrent users and zero think time. The test creates a three level site hierarchy.






- Hardware independent
- Persistence Manager independent
- Cluster independent
- allows to create height load
- allows to create large amount of content
- allows to test with many concurrent users
- allows to test different kind of content structures
- allows to test different kind of CQ operations at the same time
- allows to measure infrastructure performance
The test was designed to use the cloud for the test execution. The cloud offers the possibility to run the same test on different hardware, OS, java versions and on 32 or 64 bit architecture.
Can also be used to test the cluster. Configure the hostname of the master or a slave node to run the test against this node. The master and one or more slave nodes can also be tested simultaneously.
Testing the cluster functionality inside the Cloud allows you to switch between one machine, multiple machines in the same zone and same region, different zones but same region and different regions.

The number of pages, users, images etc. that will be created can be configured. Following is the default for our nightly build tests:

Nota:
"These are all “write tests," simulating Individual CQ5 end-user browser Operations and cannot be compared to bare-bone repository operations. Tests performed: running Windows 2008 Server”.

The following results are from a test on a medium amazon machine.
- Create 1000 pages with 5000 page updates: 225 seconds
- Import 50 Images: 79 seconds
- Create 2000 users: 101 seconds

7.5 GB memory |
4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each) |
850 GB instance storage |
64-bit platform |
I/O Performance: High |
API name: m1.large |

Increasing the CPU power by 26 times increases the throughput by 11 times and with very fast I/0 even by 24 times.
Toughday-5.6.1.jar is a command line tool to quickly stress test your system. It is a derivative of the Tough Day test. It allows you to create pages, users, tags and images on a CQ instance. You can measure your server performance with a benchmark.
java -Xmx1024m -Dhostname=localhost -Dport=4502 -DuploadImage.count=10 -jar toughday-5.6.1.jar uploadImage
This would unpack the jar into a toughday folder in the current directory. After that it starts an uploadImage test with 10 images to a CQ instance which is running on localhost:4502.
The tool supports CQ 5.6.1
Important folder and files:
- toughday.properties
Contains the default values for the tests - tasks
Contains the tests, each test contains his own folder - task/build.fragment
Which is an ant fragment file which contains at least one ant target with the name of the test e.g. "createPages" and must be depending on the "test" target.
java -Xmx1024m -Dhostname=localhost -Dport=4502 -jar toughday-5.6.1.jar all
This runs all tests in parallel. The addTagsToGeometrixxPages test depends on the tags test so it might fail because of the timing.
Descargar
Nota:
This JAR file was updated for AEM 6.1 due to the CRSF protection feature. Using the earlier version of this JAR file will result in the following errors:
"com.adobe.granite.csrf.impl.CSRFFilter isValidRequest: empty CSRF token - rejecting"
"com.adobe.granite.csrf.impl.CSRFFilter doFilter: the provided CSRF token is invalid"
java -Xmx1024m -Dhostname=localhost -Dport=4502 -DcreatePages.toplevels=2 -DcreatePages.sublevels=2 -DcreatePages.subsublevels=2 -DcreatePages.concurrentUsers=3 -DcreatePages.rampup=1 -DcreatePages.thinkt=5 -DcreatePages.activate=true -DcreatePages.delete=true -jar toughday-5.6.1.jar createPages
java -Xmx1024m -Dhostname=localhost -Dport=4502 -Dhostname.slave=localhost -Dport.slave=8080 -DcreatePagesCluster.concurrentUsers=10 -DcreatePagesCluster.rampup=1 -DcreatePagesCluster.loop=10 -jar toughday-5.6.1.jar createPagesCluster
java -Xmx1024m -Dhostname=localhost -Dport=4502 -DCQ5MSMNewSite.count=10 -DCQ5MSMNewSite.testplan=CQ5MSMNewSite-1.0.jmx -jar toughday-5.6.1.jar CQ5MSMNewSite
Create a number of different images in the repository. This also triggers some DAM workflows
(metadata extraction, renditions etc.).
java -Xmx1024m -Dhostname=localhost -Dport=4502 -DuploadImage.count=10 -jar toughday-5.6.1.jar uploadImage
Execute the createPages and uploadImages tasks and measure the time they require to run. This enables you to compare the results with those of an Amazon m1-large instance.
java -Xmx1024m -Dhostname=localhost -Dport=4502 -jar toughday-5.6.1.jar benchmark
java -Xmx1024m -Dhostname=localhost -Dport=4502 -jar toughday-5.6.1.jar tags
java -Xmx1024m -Dhostname=localhost -Dport=4502 -jar toughday-5.6.1.jar addTagsToGeometrixxPages
Uploads a number of PDFs. This also triggers certain DAM workflows (used for metadata extraction, etc.).
java -Xmx1024m -Dhostname=localhost -Dport=4502 -DuploadPdf.count=10 -jar toughday-5.6.1.jar uploadPdf
From 5.5 onwards there are new author scenario tests which simulate all GET and POST requests (97% GET, 3% POST).
To achieve this we have defined a scenario that simulates a regular use case for authors. This includes steps including creating a page, adding some components, rating some content, activating some pages and deleting pages.
The Authoring Scenario uses the Geometrixx Demo Site:
- Login into CQ (http://<hostname>:<port>)
- Open WebSites
- Navigate to Geometrixx Demo Site --> English
- Create a new Page with a random title and the Geometrixx Content Page template
- Open the testPage
- Add a Sitemap component to the paragraph system
- Add a Flash component to the paragraph system
- Select the Movies tab inside the Content Finder
- Drag & Drop the item triangles.swf to the Flash Component
- Add a Text & Image component to the paragraph system
- Select the Images tab inside the Content Finder
- Scroll down and drag & drop the file geo_hq.jpg to the Image component
- Edit the Text & Image component and write following text:
"Our triangles meet all ISO and DIN industry standards, GeoMetrixx# gives you the ability to effortlessly offer the perfect product and support." - Add a Tag Cloud to the paragraph system
- Edit the Tag Cloud, set Tags to Display to All tags
- Add a Ratings component to the paragraph system
- Add a Comments component to the paragraph system
- Activate the Page with the depending assets inside the Siteadmin
- Open the Page
- Delete the Page inside the Siteadmin
java -Xmx1024m -Dhostname=localhost -Dport=4502 -Dauthoring.loop=2 -Dauthoring.thread=2 -jar toughday-5.6.1.jar authoring
java -Xmx1024m -Dhostname=localhost -Dport=4502 -jar toughday-5.6.1.jar all