Skip to contentSkip to conversation

Locking comment on shrink_caches()

DISCUSSION David S. Miller 2 participants 2 messages Sep 25, 2001 – Sep 26, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

From: Gerrit Huizenga <[email protected]>
Date: Tue, 25 Sep 2001 15:15:13 PDT

I'm very curious as to what workloads are showing pagecache_lock as a bottleneck. We haven't noticed this particular bottleneck in most of the workloads we are running. Is there a good workload that shows this type of load?

Again, I defer to Ingo for specifics, but essentially something like specweb99 where the whole dataset fits in memory.

Franks a lot,
David S. Miller
[email protected]

#2 lore raw
Quoted 7 lines · David S. Miller

I'm very curious as to what workloads are showing pagecache_lock as a bottleneck. We haven't noticed this particular bottleneck in most of the workloads we are running. Is there a good workload that shows this type of load?

Again, I defer to Ingo for specifics, but essentially something like specweb99 where the whole dataset fits in memory.

it was SPECweb99 tests done in 32 GB RAM, 8 CPUs, where the pagecache was nearly 30 GB big. We saw visible pagecache_lock contention on such systems. Due to TUX's use of zerocopy, page lookups happen at a much larger frequency and they are not intermixed with memory copies - in contrast with workloads like dbench.

Ingo