Re: -mmX 4G patches feedback [numbers: how much performance impact]

[Martin J. Bligh]

> anyway, i can only repeat what i said last year in the announcement
> email of the 4:4 feature:
> 
>    the typical cost of 4G/4G on typical x86 servers is +3 usecs of
>    syscall latency (this is in addition to the ~1 usec null syscall
>    latency). Depending on the workload this can cause a typical
>    measurable wall-clock overhead from 0% to 30%, for typical
>    application workloads (DB workload, networking workload, etc.).
>    Isolated microbenchmarks can show a bigger slowdown as well - due to
>    the syscall latency increase.
> 
> so it's not like there's a cat in the bag.

I don't see how you can go by the cost in syscall latency ... the real 
cost is not the time take to flush the cache, it's the impact of doing
so .... such microbenchmarks seems pointless. I'm not against 4/4G at all,
I think it solves a real problem ... I just think latency numbers are a 
bad way to justify it - we need to look at whole benchmark runs.

M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/