[Lustre-devel] COS performance issues
Alexander.Zarochentsev at Sun.COM
Sun Oct 12 08:51:56 PDT 2008
On 11 October 2008 20:00:10 Andreas Dilger wrote:
> On Oct 08, 2008 15:44 +0400, Alexander Zarochentsev wrote:
> > I think the problem is that COS defers processing of replies to
> > transaction commit time. When commit happens, MDS has to process
> > thousands of replies (about 14k replies per commit in the test 3.a)
> > in short period of time. I guess the mdt service threads all woken
> > up and spin trying to get the service svr_lock. Processing of new
> > requests may also suffer of this.
> Can you please explain what replies are being blocked? It can't be
> the create replies or the clients would be blocked waiting after
> starting a single create each.
> I think the thread and lock contention is only part of the issue - if
> all of these replies are blocked until transaction commit this wastes
> all of the bandwidth on the network while the replies are being held.
as Eric explained already, replies are sent already but the reply state
objects remain in memory. The cleanup process is almost serialized by
per-service spinlock. It might be only a part of the problem but the
first task to solve.
> Cheers, Andreas
Alexander "Zam" Zarochentsev
Lustre Group, Sun Microsystems
More information about the lustre-devel