Reproduce the user journey
Include login, resource discovery, file access, messaging, invited users and any collaborative application that matters to your pilot.
TECHNICAL EVIDENCE
Performance.
With the context attached.
The company materials document virtual-desktop and messaging stress tests on a CCC configuration. Read the workload, observations and limits behind the figures.
2.7 GHzDual-core CPU in the documented setup
4 GBRAM in the documented setup
300Simultaneous desktop login attempts
18,000Messages per minute in the messaging workload
Reported company tests on a specific CCC configuration. These figures are not a capacity guarantee for another device, workload or deployment.
DESKTOP CONNECTION TEST
Many users.
One login workload.
| Test element | Reported condition or observation |
|---|---|
| Participants | 300 users attempt simultaneous login and connection to their personal virtual desktops |
| Identity | Each participant uses a different username and password |
| Connection outcome | All participants are reported to have connected successfully |
| Fastest login | 0.5 seconds, reported as the shortest observed login time |
| Module behaviour | The materials report that modules continued to operate smoothly |
| What is not supplied | A latency distribution, repeated-run methodology and a present production benchmark are not supplied |
MESSAGE EXCHANGE TEST
A shared conversation.
At a defined load.
600sending users
×30messages per user / minute
=18,000messages sent / minute
| Test element | Reported condition or observation |
|---|---|
| Send rate | One message every two seconds from each of 600 sending users |
| Fan-out | Each message is simultaneously delivered to nine other users in the CoSpace |
| Delivery | All messages are reported to have been delivered, received and recorded |
| Server response | The source reports that load returned to normal immediately after sending ended |
| Interpretation | This defines the documented message workload; it does not establish latency or delivery behaviour under every usage pattern |
APPENDIX LOAD MODEL
Observed tests.
Separate capacity interpretations.
| Documented statement | How to interpret it |
|---|---|
| Five CCCs: 6,000 users and 1,650 simultaneous logins | A multi-device appendix result reported in the company materials |
| One CCC: 1,200 users and 330 simultaneous logins | A per-device interpretation of the multi-device result |
| One CCC: 600 users at 30 messages per minute | The message workload documented in the appendix |
| One CCC: 1,200 users at 15 messages per minute | An alternative load interpretation at the same aggregate send rate |
| Conservative estimate: 600 users | A company estimate acknowledging differences in CPU brand and configuration |
| Marketed configuration: 50 users | The source separately describes a deliberately lower marketed user figure |
User population, simultaneous connections and active messaging load describe different dimensions. They should not be combined into a single headline capacity claim.
A PRACTICAL ACCEPTANCE PLAN
Test the work
you actually need.
Measure the distribution
Record median and tail latency, failure rates and repeated-run behaviour. The shortest login time alone is insufficient.
Include the environment
Use the intended CPU, memory, storage, network and browser settings. Add representative application and file workloads.
Test the boundary conditions
Exercise permission changes, participant removal, storage growth, backup and recovery. Acceptance includes operating behaviour.
YOUR NEXT CHAPTER
Define a workload.
Validate an environment.
Start with the people, resources and infrastructure you already have. Build a clearer picture of what collaboration could become.
Build your collaboration brief