Description of problem: As per the latest perf runs (on glusterfs-6.0.6 and nfs-ganesha-2.7.3-5) , there is regression in RENAME workload by 17.05 % over NFSv4.1 protocol https://docs.google.com/spreadsheets/d/1r-peEBfHjds27ISwuikWgPJ4djAGQqqZu397wGrWtE4/edit#gid=525127835 Note: On fuse the same workload regressed by around ~5-6% (bug1713890) Version-Release number of selected component (if applicable): glusterfs-6.0.6 nfs-ganesha-2.7.3-5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
In gdb I saw client4_0_lookup hitting 9-10 times, server4_0_lookup hitting 20254 and posix_lookup hitting 20250 times on gluster side. While gluster profile was showing 20255 calls happening for lookup. Soumya, what's your say on the difference between number of calls of client4_0_lookup and server4_0_lookup.