Bug 751327 - Performance smoke test
Summary: Performance smoke test
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 751295
TreeView+ depends on / blocked
 
Reported: 2011-11-04 10:52 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-05-19 23:42:40 UTC
Embargoed:

Attachments (Terms of Use)

Description Joshua Wulf 2011-11-04 10:52:36 UTC 
Get a reasonable sized dataset (perhaps clone the EAP6 one), and a content spec with 100+ topics in it.

For each release run a build using:

1. Local CSProcessor database, local Skynet Database
2. Local CSProcessor database, remote Skynet Database

and post the results in the Release Note for the build.
Comment 1 Joshua Wulf 2011-11-04 10:55:54 UTC 
Do the same test pushing it as new content spec each time as well.

So 4 tests:

Push Content spec
  Local, Local
  Local, Remote

Build Content Spec
  Local, Local
  Local, Remote
Comment 2 Lee Newson 2011-11-07 02:18:16 UTC 
Along with this, I plan to add a parameter that you can set in the client (--exec-time possibly) that will show the execution time of each request. This was discussed a while ago but never added as a bug to be implemented.
Comment 3 Lee Newson 2011-11-21 04:36:06 UTC 
The --exec-time command has been added for push and build commands in client build 0.14.0 and web server version 0.17.0
Comment 4 Lee Newson 2012-05-19 23:42:40 UTC 
Since I can no longer do much about network times as we now use the Skynet REST interface I'm going to close this.
Note You need to log in before you can comment on or make changes to this bug.