Uncountable Nouns: Traffic, Latency, Data, Evidence

LESSON

Technical English: Nouns, Articles, and Countability

007 20 min beginner

Uncountable Nouns: Traffic, Latency, Data, Evidence

By the end of this lesson, you will be able to...

  • Recognize when traffic, latency, data, or evidence names an amount or body of information rather than separate objects.

  • Avoid false singular and plural forms such as a traffic, three latencies, and an evidence in their general meanings.

  • Add a natural unit or subtype when the reader needs to count: data points, latency measurements, traffic spikes, or pieces of evidence.

Idea in one sentence: When a technical noun names an amount or body of information, describe how much it is or add a unit before trying to count it.

Core Insight

An incident commander asks for the evidence behind a latency alert. The dashboard gives four measurements:

Traffic: 2.4 GB/s
Latency: 900 ms
Data: 18 GB
Evidence: logs and traces

A rushed update turns those measurements into awkward plural nouns:

We saw two traffics, three latencies, 18 datas, and an evidence.

The problem is not that the team lacks numbers. The problem is that the numbers describe amounts or measurements, not separate things called traffics, latencies, or datas.

Write the update like this:

Traffic reached 2.4 GB/s. Latency reached 900 ms. We collected 18 GB of data and found evidence in the logs and traces.

Traffic, latency, data, and evidence are often uncountable nouns in these meanings. They behave like an amount, material, phenomenon, or body of information. You can measure them, compare them, or identify their source without treating the noun itself as a list of separate objects.

The Small Situation

Mina is writing a metric note for a payment incident. She has two kinds of information:

Her first draft mixes the two:

Three requests failed because the service received many traffics. We saw two latencies above 900 ms and collected an evidence from the logs. The datas confirm the error.

The reader can guess the intended meaning, but the noun forms hide the units. Mina revises the note:

Three requests failed because the service received heavy traffic. We recorded two latency measurements above 900 ms and collected evidence from the logs. The data confirms the error.

The countable nouns keep their number: three requests. The amount nouns stay uncountable: traffic, evidence, data. When Mina needs to count observations, she adds the countable head noun measurements.

The Naive Idea

After learning that requests and workers can take numbers, a learner may try to use the same pattern everywhere:

one traffic
two latencies
three datas
an evidence

This is tempting because each word refers to something real and measurable. But “measurable” does not mean “countable.” Water can be measured in liters without usually becoming three waters. Latency can be measured in milliseconds without usually becoming three latencies.

Use the amount directly:

more traffic
high latency
enough data
strong evidence

Or add a unit, event, or subtype that has separate members:

three traffic spikes
two latency measurements
three data points
four evidence items

The new noun is the countable unit. Spikes, measurements, points, and items can take one, two, or three.

How to Recognize an Uncountable Meaning

Use three practical tests.

Test 1: Ask “How much?”

How much traffic arrived? 2.4 GB/s arrived.
How much latency did the request have? 900 ms.
How much data did we collect? 18 GB.
How much evidence do we have? Enough evidence from the logs.

If the natural question asks for an amount, keep the noun uncountable or add a unit.

Test 2: Do not place a/an directly before the amount noun

In the general meanings used here, write:

traffic increased
latency was high
data was missing
evidence was weak

Not:

a traffic increased
a latency was high
an evidence was weak

You can use a/an when a countable noun follows:

a traffic spike
a latency measurement
a data point
a piece of evidence

Test 3: Add a unit when the reader needs a count

The choice of unit changes what the reader can understand:

We collected data.
We collected three datasets.
We collected 18 GB of data.
We collected three data exports.

The first sentence describes information generally. The others count a volume, a dataset, or an export. The unit should match the engineering question.

The Core Forms

General amount or information A natural counted unit Example
traffic traffic spike, request, GB of traffic Traffic increased by 30%. / Two traffic spikes appeared.
latency latency measurement, latency spike, milliseconds Latency reached 900 ms. / Three latency measurements exceeded 900 ms.
data data point, record, dataset, GB of data We need more data. / We sampled 500 records.
evidence piece/item of evidence, log entry, trace, test result We found evidence in the logs. / Three log entries support the claim.

This table is a repair strategy, not a list of forbidden words. When an amount noun needs a number, ask what the system actually produced: a spike, a measurement, a record, a trace, or a result.

A Worked Trace: From Metrics to a Clear Note

Start with the raw incident dashboard:

Requests failed: 3
Traffic: 2.4 GB/s
Latency samples above 900 ms: 2
Data captured: 18 GB
Log entries supporting the cause: 4

Turn it into a note in four steps.

Input Decision Output What changed
Requests failed: 3 Keep the countable object and plural. Three requests failed. The reader sees the number of affected requests.
Traffic: 2.4 GB/s Describe an amount, not separate traffics. Traffic reached 2.4 GB/s. The unit measures the amount.
Latency samples above 900 ms: 2 Count the samples, not “latencies.” Two latency measurements exceeded 900 ms. measurements provides the countable head.
Data captured: 18 GB Use of data after the amount. We captured 18 GB of data. The amount is explicit without pluralizing data.
Log entries: 4 Count the entries as evidence. Four log entries support the diagnosis. The evidence source is countable.

The finished note is:

Three requests failed. Traffic reached 2.4 GB/s. Two latency measurements exceeded 900 ms. We captured 18 GB of data, and four log entries support the diagnosis.

The input was a dashboard with mixed units. The transition selected a natural countable unit for each row. The output separates objects, amounts, and evidence so a reader can compare impact without guessing what each number counts.

Compare the naive version:

Three requests failed. Two traffics and three latencies were high. We captured 18 datas and four evidences.

It puts numbers in the sentences, but the numbers attach to the wrong nouns. More numbers do not automatically create more precision.

Check: The team recorded three observations of request latency. Which sentence uses a countable unit naturally?

A) We recorded three latencies.
B) We recorded three latency measurements.
C) We recorded three latencys.

Think first, then reveal.

Answer: B. Latency measurements names three separate observations. The noun latency remains an amount or property inside the compound.

Specific Amounts Still Use the

Uncountable does not mean “never use an article.” The earlier reader-state model still applies when the amount is identifiable:

Traffic increased during the sale.
The traffic from mobile clients increased during the sale.

The first sentence describes traffic generally in this event. The second identifies a particular source-defined amount.

Latency was high.
The latency for request 1842 was 900 ms.

The second phrase points to one known measurement. It does not turn latency into a normal countable noun; the identifying phrase gives the reader one specific amount to inspect.

We need more data.
The data from the failed requests is incomplete.

In these sentences, data is treated as a mass noun meaning information. Some technical and academic styles treat data as a plural noun and write the data are. Both conventions exist. Follow the style used by your team, but do not switch randomly inside one report. When you want to avoid the convention question, name the unit: the records are incomplete or the data points are incomplete.

Data and Evidence Need a Unit or Source

Data and evidence are especially easy to make vague because they can contain many different things:

The data is useful.
The evidence is strong.

These sentences can be grammatical, but they do not tell the reader what is inside the body of information. Add a source or a unit when the decision depends on it:

The checkout records are incomplete.
The evidence from four log entries supports the diagnosis.
The trace samples show that the timeout started before the retry.

The source can make an uncountable noun specific without making it countable. The unit can make the internal members countable when that is the useful view.

Trade-offs and Limits

The main trade-off is between natural amount language and visible counting units. Saying Traffic increased is compact and useful when the percentage or rate is already on the dashboard. Saying Traffic reached 2.4 GB/s costs a few more words but gives the reader a comparable measurement.

Adding a unit also narrows the claim. Evidence can include logs, traces, tests, and observations. Four log entries is easier to count, but it may hide other evidence. Count the unit that supports the decision, not the unit that merely makes the sentence look precise.

This lesson does not claim that every noun has one permanent category. Technical meaning can change the grammar:

Data is missing.              # information as an amount
The data points are missing.  # separate observations
Evidence supports the claim.  # information as a body
Three pieces of evidence support the claim.  # counted units

The signal is the question the reader needs answered. If the question is “How much information?” keep the amount noun. If it is “How many records, measurements, or traces?” name the countable unit.

Check: Which sentence is the clearest repair for We found two evidences in the log?

A) We found two evidence in the log.
B) We found two pieces of evidence in the log.
C) We found two evidences in the log.

Think first, then reveal.

Answer: B. Evidence remains uncountable, while pieces provides the countable unit. If the evidence consists of log entries, an even more precise version is We found two log entries that support the diagnosis.

Common Confusions

Confusion: measurable means countable

Why it is tempting:

Traffic, latency, and data appear next to numbers on every dashboard.

Better model:

Measurement answers “how much” or “how high,” not automatically “how many.” Write 2.4 GB of traffic, 900 ms of latency, or 18 GB of data.

Confusion: add -s to every technical noun after a number

Why it is tempting:

Three requests and two workers work, so the pattern feels universal.

Better model:

The number needs a countable head noun. Use three latency measurements, not three latencies; use four log entries, not four evidences.

Confusion: the makes an uncountable noun countable

Why it is tempting:

The latency seems to point to one thing.

Better model:

The identifies one amount or measurement in context. It does not make latency pluralizable. Use the latency for request 1842 or a latency measurement when the unit matters.

Practice

Rewrite this metric note for an engineer who must decide whether to roll back:

We saw three traffics during the deploy. The service had two latencies above 1 second and collected an evidence. The datas contain many useful information. Four requests also failed.

Try it before reading the model.

Model answer:

Traffic spiked three times during the deploy. The service recorded two latency measurements above 1 second and collected evidence from the logs. The data contains useful information. Four requests also failed.

Another precise answer could say We saw three traffic spikes or The data points contain useful information, depending on the source. A strong answer should:

Daily Practice Lines

The first line reuses the countable pattern from lesson 006. The second keeps traffic as an amount and gives it a unit. The third keeps evidence uncountable while connecting the language to an engineering decision.

Resources

Key Takeaways

PREVIOUS Countable Nouns: Request, Error, Worker, Region NEXT Some, Any, Much, Many, Few, and Little