diff options
author | Dave Chinner <david@fromorbit.com> | 2010-09-02 15:14:38 +1000 |
---|---|---|
committer | Dave Chinner <david@fromorbit.com> | 2010-09-02 15:14:38 +1000 |
commit | 9bc08a45fb117c696e4940cfa1208cb1cc7a2f25 (patch) | |
tree | 610e4cb520d62c4ad6ae0f20ddd64cd15520c33a /fs/bad_inode.c | |
parent | 2bfc96a127bc1cc94d26bfaa40159966064f9c8c (diff) | |
download | op-kernel-dev-9bc08a45fb117c696e4940cfa1208cb1cc7a2f25.zip op-kernel-dev-9bc08a45fb117c696e4940cfa1208cb1cc7a2f25.tar.gz |
xfs: improve buffer cache hash scalability
When doing large parallel file creates on a 16p machines, large amounts of
time is being spent in _xfs_buf_find(). A system wide profile with perf top
shows this:
1134740.00 19.3% _xfs_buf_find
733142.00 12.5% __ticket_spin_lock
The problem is that the hash contains 45,000 buffers, and the hash table width
is only 256 buffers. That means we've got around 200 buffers per chain, and
searching it is quite expensive. The hash table size needs to increase.
Secondly, every time we do a lookup, we promote the buffer we find to the head
of the hash chain. This is causing cachelines to be dirtied and causes
invalidation of cachelines across all CPUs that may have walked the hash chain
recently. hence every walk of the hash chain is effectively a cold cache walk.
Remove the promotion to avoid this invalidation.
The results are:
1045043.00 21.2% __ticket_spin_lock
326184.00 6.6% _xfs_buf_find
A 70% drop in the CPU usage when looking up buffers. Unfortunately that does
not result in an increase in performance underthis workload as contention on
the inode_lock soaks up most of the reduction in CPU usage.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'fs/bad_inode.c')
0 files changed, 0 insertions, 0 deletions