Chapter 2 Flashcards

Performance Measurement Fundamentals

1
Q

Vocab

Measurement

A

The process of quantifying and evaluating the attributes of a software product or process to assess its quality, performance, and progress.

Used to assess key-performance-indicators (KPIs) and metrics

Examples include:
* Time To First Byte (TTFB)
* Peak Response Time
* Throughput
* Error rates
* Resource utilization (e.g., CPU, memory, disk I/O)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Vocab

Metric

A

Derived from measurements

A standardized unit of measurement that provides a snapshot of the system’s behavior under various loads, scenarios, or conditions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Why are measurements and metrics necessary?

A
  • Defines goals for
  • Evaluates the results of

performance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the 6 project risks that can occur without well defined measurements and metrics?

Note project vs product risks from the CTFL material

A
  • Unknown if performance levels are acceptable for operational objectives
  • Performance requirements aren’t defined in measurable terms
  • May not be possible to ID trends that can predict lower levels of performance
  • Cannot compare actual to expected test results due to lack of baseline
  • Results are subjective rather than objective
  • Results are not understandable, thereby breaking one of the principles
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

For Fun

Define SMART goals

Helpful for testing and even personal/professional growth

A
  • Specific - Clearly define what you want to achieve, avoiding vague or general statements.
  • Measurable - Quantify your goal, allowing you to track progress and measure success.
  • Achievable - Ensure the goal is realistic and attainable based on your resources and capabilities.
  • Realistic - Align your goal with your values and long-term objectives, making it meaningful and relevant.
  • Time-bound - Set a specific deadline or timeframe for achieving the goal, providing focus and motivation.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the three contextual environments of perf testing?

A
  • Business
  • Operational
  • Technical
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are some examples of technical environments?

A
  • Web-based
  • Mobile
  • IOT
  • Desktop client devices
  • Server-side processing
  • Mainframe
  • Databases
  • Networks
  • Embedded
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are some examples of technical metrics?

A
  • Response time
  • Resource utilization
  • Throughput rate of key transaction
  • Batch processing time
  • Numbers of errors that would impact performance
  • Completion time
  • Background load on shared resources
  • Software metrics (such as complexity)

See 2.1.2

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are some examples of business metrics?

A
  • Business process efficiency
  • Throughput of data, transactions, and other units of work
  • Service level agreements (SLAs) and any violations
  • Scope of usage
  • Concurrency of usage
  • Timing of usage

See 2.1.2

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are some examples of operational metrics?

A
  • Operational processes
  • System restoration
  • Alerts and warnings

Things that aren’t user-facing in nature

See 2.1.2

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the goal-question-metric (GQM) approach to metric selection?

A
  1. Establish the goals
  2. Ask questions to know when the goals have been achieved

Metrics are associated with each question to ensure the answer is mesurable.

The process may be iterative, as more or better metrics might need to be derived.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Define the “probe effect”

A

When the metrics collection effort impacts the performance of the system. The effort should no more than minimally impact.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Is it ok to use more than one tool to collect metrics?

A

Multiple tool usage is common enough, but care must be taken. Redundant metrics might be collected and other problems introduced.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are 3 sources of performance metrics?

A
  • Performance Test tools
  • Performance Monitoring tools
  • Log analysis tools
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Describe Performance Test Tools

A
  • They all provide measures and metrics.
  • Some report in a text format, others use graphics.
  • Many allow the ability to export results for reporting.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Describe Performance Monitoring Tools

A
  • Often used to supplement performance test tools.
  • Can monitor on an ongoing basis and alert sys admins to threshold violations and errors.
  • These can also be used to detect and report suspicious behavior.
17
Q

Describe Log Analysis tools

A

These can scan server logs and compile metrics.

Errors, alerts, and warnings are usually found in server logs. Some of the events recorded are:
* High resource usage
* Memory errors and warnings
* Deadlocks and multithreading issues (especially for databases)
* Database errors

18
Q

Difference between functional and non-functional (performance) test requirements?

A

Performance requirements usually aren’t directly articulated by the business the way functional requirements are.

Additionally, performance issues can be hidden under seemingly good results, such as resourcing issues.

Results from performance tests will always rely on the context and type of test being run.