Skip to contentSkip to conversation

IO degradation in 2.4.17-pre2 vs. 2.4.16

DISCUSSION Dan Maas 5 participants 5 messages Dec 11, 2001 – Dec 12, 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]

Dan Maas

author
#1 lore raw
Quoted 9 lines
Quoted 7 lines

Yes, throughtput-only tests will have their numbers degradated with the change applied on 2.4.16-pre2.

The whole thing is just about tradeoffs: Interactivity vs throughtput.

I'm not going to destroy interactivity for end users to get beatiful dbench numbers.

Latency is more of an issue for end user machines.

Time for CONFIG_OPTIMIZE_THROUGHPUT / CONFIG_OPTIMIZE_LATENCY ?

Dan

#2 lore raw
Quoted 11 lines · Dan Maas
Quoted 9 lines
Quoted 7 lines

Yes, throughtput-only tests will have their numbers degradated with the change applied on 2.4.16-pre2.

The whole thing is just about tradeoffs: Interactivity vs throughtput.

I'm not going to destroy interactivity for end users to get beatiful dbench numbers.

Latency is more of an issue for end user machines.

Time for CONFIG_OPTIMIZE_THROUGHPUT / CONFIG_OPTIMIZE_LATENCY ?

That would be the best thing to do, yes.

#3 lore raw
Quoted 2 lines
Quoted 1 line

Time for CONFIG_OPTIMIZE_THROUGHPUT / CONFIG_OPTIMIZE_LATENCY ?

That would be the best thing to do, yes.

/proc/sys not CONFIG_..

#4 lore raw
Quoted 4 lines · Alan Cox
Quoted 2 lines
Quoted 1 line

Time for CONFIG_OPTIMIZE_THROUGHPUT / CONFIG_OPTIMIZE_LATENCY ?

That would be the best thing to do, yes.

/proc/sys not CONFIG_..

YES!

Much much preferable...

cu

jjs

#5 lore raw
In reply to Marcelo Tosatti
Quoted 5 lines · Alan Cox
Quoted 3 lines
Quoted 2 lines

Time for CONFIG_OPTIMIZE_THROUGHPUT / CONFIG_OPTIMIZE_LATENCY ?

That would be the best thing to do, yes.

/proc/sys not CONFIG_..

/proc/sys/vm/bdflush, to be precise.

I thought we discussed all this?

-