Skip to content

GFS2: inplace_reserve performance improvements

Bob Peterson cluster-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 2 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Cluster-devel] [PATCH 0/2] GFS2: inplace_reserve performance improvements

----- Original Message -----

Quoted 9 lines

I think what's happening for us is that the work that needs to be done to release an rgrp lock is happening pretty fast and is about the same in all cases, so the stats are not providing a meaningful distinction. We see the same lock (or small number of locks) bouncing back and forth between nodes with neither node seeming to consider them congested enough to avoid, even though the FS is <50% full and there must be plenty of other non-full rgrps.

--
Tim Smith <[email protected]>

Hi Tim,

Interesting.
I've done experiments in the past where I allowed resource group glocks to take advantage of the "minimum hold time" which is today only used for inode glocks. In my experiments it's made no appreciable difference that I can recall, but it might be an interesting experiment for you to try.

Steve's right that we need to be careful not to improve one aspect of performance while causing another aspect's downfall, like improving intra-node congestion problems at the expense of inter-node congestion.

Regards,

Bob Peterson