Assuming that these numbers are with KRB5I and KRB5P, then the window size is a multiple of the number of threads. The old code might be using a fixed number of a bigger window size. How many rpc max threads are you using? The default is 200, I think and it should have a big window size though.

Do you see any perf issues with plain KRB5 or with AUTH_SYS between 2.5 and 3.3. Generally speaking 3.3 should have similar or better perf compared to ganesha2.5 with AUTH_SYS.

Regards, Malahal.

On Mon, Oct 12, 2020 at 2:33 PM Chakra Divi <chakragithub@gmail.com> wrote:

Thanks Malahal, ntirpc window size fixes are working. But we are seeing a performance degradation on v3 when compared with v2.5.
iozone taking 50% more time to complete on the same setup with v3 version. IO operations with bigger block sizes - seems like having the impact.

With 3.3 – after fix
real 36m37.985s
user 0m1.974s
sys 1m33.561s

v2.5 – working version
real 23m21.187s
user 0m1.797s
sys 1m16.537s

Please let me if you need anything more from my setup like traces...to get hold of the issue
_______________________________________________
Devel mailing list -- devel@lists.nfs-ganesha.org
To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org