Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pullup NTIRPC through #124
Hi, Girjesh Rajoria wrote on Mon, Mar 19, 2018 at 10:47:09PM +0530: >> + tail -21 ../dbenchTestLog.txt >> >> OperationCountAvgLatMaxLat >> -- >> Deltree102 9.79927.590 >> Flush 284316 1.637 203.259 >> Close 2979801 0.007 0.330 >> LockX13208 0.007 0.079 >> Mkdir 51 0.011 0.059 >> Rename 171774 0.073 0.463 >> ReadX 6358865 0.01038.319 >> WriteX 2022375 0.04840.888 >> Unlink 819204 0.09038.363 >> UnlockX 13208 0.006 0.063 >> FIND_FIRST 1421549 0.04438.320 >> SET_FILE_INFORMATION330438 0.024 0.310 >> QUERY_FILE_INFORMATION 644319 0.004 0.242 >> QUERY_PATH_INFORMATION 3676827 0.01540.851 >> QUERY_FS_INFORMATION674193 0.01037.783 >> NTCreateX 4056560 0.049 122.097 >> >> >> Where are the iozone results from ../ioZoneLog.txt? > > iozone suite doesn't give outputs result as dbench. So iozone test checks > for successful completion and print message of success in the log. In cases > where the test fails, it'll print error due to which test failed from > ../ioZoneLog.txt. I think it's great to have this kind of dbench stats, and would be awesome if we can have some raw figures from iozone as well (I think it can output the results in csv format at least?) jenkins can also take performance metrics from jobs and we could have graphs of the performance over time if it keeps these metrics a bit longer than the actual jobs (for example with the performance plugin[1], but there might be other ways) On an individual basis as the tests are on VMs with various loads the results will probably flicker a bit, but on a whole we should be able to identify what week(s) introduced slowdowns/speedups after the fact quite nicely if we can achieve that! :) [1] https://plugins.jenkins.io/performance -- Dominique -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pullup NTIRPC through #124
On Tue, Mar 20, 2018 at 08:59:21AM +0100, Dominique Martinet wrote: > Hi, > > Girjesh Rajoria wrote on Mon, Mar 19, 2018 at 10:47:09PM +0530: > >> + tail -21 ../dbenchTestLog.txt > >> > >> OperationCountAvgLatMaxLat > >> -- > >> Deltree102 9.79927.590 > >> Flush 284316 1.637 203.259 > >> Close 2979801 0.007 0.330 > >> LockX13208 0.007 0.079 > >> Mkdir 51 0.011 0.059 > >> Rename 171774 0.073 0.463 > >> ReadX 6358865 0.01038.319 > >> WriteX 2022375 0.04840.888 > >> Unlink 819204 0.09038.363 > >> UnlockX 13208 0.006 0.063 > >> FIND_FIRST 1421549 0.04438.320 > >> SET_FILE_INFORMATION330438 0.024 0.310 > >> QUERY_FILE_INFORMATION 644319 0.004 0.242 > >> QUERY_PATH_INFORMATION 3676827 0.01540.851 > >> QUERY_FS_INFORMATION674193 0.01037.783 > >> NTCreateX 4056560 0.049 122.097 > >> > >> > >> Where are the iozone results from ../ioZoneLog.txt? > > > > iozone suite doesn't give outputs result as dbench. So iozone test checks > > for successful completion and print message of success in the log. In cases > > where the test fails, it'll print error due to which test failed from > > ../ioZoneLog.txt. > > I think it's great to have this kind of dbench stats, and would be > awesome if we can have some raw figures from iozone as well (I think it > can output the results in csv format at least?) > > > jenkins can also take performance metrics from jobs and we could have > graphs of the performance over time if it keeps these metrics a bit > longer than the actual jobs (for example with the performance plugin[1], > but there might be other ways) > > On an individual basis as the tests are on VMs with various loads the > results will probably flicker a bit, but on a whole we should be able to > identify what week(s) introduced slowdowns/speedups after the fact quite > nicely if we can achieve that! :) Note that the tests in the CentOS CI run on different physical hosts. When a test is started, one or more machines are requested, and the scheduler (called Duffy) just returns a random system. This means that the performance results might differ quite a bit between runs, even for the same change-set. See https://wiki.centos.org/QaWiki/PubHardware for details about the hardware. So except for the performance results, it may be useful to gather some details about the hardware that was used. Niels -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pullup NTIRPC through #124
Yeah, except for drastic changes, we cannot take much away from variations in Jenkins runs, I think. Even if we know what hardware it's running on, we can't know how loaded it is. Daniel On Tue, Mar 20, 2018 at 4:59 AM, Niels de Vos wrote: > On Tue, Mar 20, 2018 at 08:59:21AM +0100, Dominique Martinet wrote: >> Hi, >> >> Girjesh Rajoria wrote on Mon, Mar 19, 2018 at 10:47:09PM +0530: >> >> + tail -21 ../dbenchTestLog.txt >> >> >> >> OperationCountAvgLatMaxLat >> >> -- >> >> Deltree102 9.79927.590 >> >> Flush 284316 1.637 203.259 >> >> Close 2979801 0.007 0.330 >> >> LockX13208 0.007 0.079 >> >> Mkdir 51 0.011 0.059 >> >> Rename 171774 0.073 0.463 >> >> ReadX 6358865 0.01038.319 >> >> WriteX 2022375 0.04840.888 >> >> Unlink 819204 0.09038.363 >> >> UnlockX 13208 0.006 0.063 >> >> FIND_FIRST 1421549 0.04438.320 >> >> SET_FILE_INFORMATION330438 0.024 0.310 >> >> QUERY_FILE_INFORMATION 644319 0.004 0.242 >> >> QUERY_PATH_INFORMATION 3676827 0.01540.851 >> >> QUERY_FS_INFORMATION674193 0.01037.783 >> >> NTCreateX 4056560 0.049 122.097 >> >> >> >> >> >> Where are the iozone results from ../ioZoneLog.txt? >> > >> > iozone suite doesn't give outputs result as dbench. So iozone test checks >> > for successful completion and print message of success in the log. In cases >> > where the test fails, it'll print error due to which test failed from >> > ../ioZoneLog.txt. >> >> I think it's great to have this kind of dbench stats, and would be >> awesome if we can have some raw figures from iozone as well (I think it >> can output the results in csv format at least?) >> >> >> jenkins can also take performance metrics from jobs and we could have >> graphs of the performance over time if it keeps these metrics a bit >> longer than the actual jobs (for example with the performance plugin[1], >> but there might be other ways) >> >> On an individual basis as the tests are on VMs with various loads the >> results will probably flicker a bit, but on a whole we should be able to >> identify what week(s) introduced slowdowns/speedups after the fact quite >> nicely if we can achieve that! :) > > Note that the tests in the CentOS CI run on different physical hosts. > When a test is started, one or more machines are requested, and the > scheduler (called Duffy) just returns a random system. This means that > the performance results might differ quite a bit between runs, even for > the same change-set. > > See https://wiki.centos.org/QaWiki/PubHardware for details about the > hardware. > > So except for the performance results, it may be useful to gather some > details about the hardware that was used. > > Niels > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] nss_getpwnam: name 't...@my.dom@localdomain' does not map into domain 'nix.my.dom'
On 3/19/2018 9:54 AM, Frank Filz wrote: Solved. Here's the solution in case it can help someone else. To get a certain feature in NFS Ganesha, I had to compile the V2.6 release from source. When configuring to compile, idmapd support got disabled since packages were missing: libnfsidmap-devel-0.25-17.el7.x86_64 Installed the above package and recompiled with nfsidmap support enabled and this issue went away. Users now show up properly off the NFS mount on clients. Oh, well that was a simple fix :-) I wonder if we could make changes in our cmake files to make it easier to see when stuff got left out due to missing packages? I've been caught out myself. Frank Yep, sure was an easy fix. Wouldn't mind seeing that. Maybe even a way to find out what options went into compiling packages for each distro. -- Cheers, Tom K. - Living on earth is expensive, but it includes a free trip around the sun. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] Release V2.6.1
I'd like to announce the release of the latest stable version of Ganesha: 2.6.1 This is a bugfix release, and includes the following commits: e2664ee61 (HEAD -> V2.6-stable, tag: V2.6.1) V2.6.1 cf0b642d0 Pullup to ntirpc 1.6.2 1a6daaf34 PROXY: add sample config file 9f4ef2c96 MDCACHE - Initialize dirent structs in entry early e8aae805e systemd: use sighup, not dbus to reload config 739ebc85d RADOS_KV: do copy in rados_kv_get before releasing read op fb5f859ba build: compile conf_lex.c with _GNU_SOURCE to get caddr_t definition 88803a26d specfile: fix libcephfs-devel and librgw-devel BuildRequires 1f3f98bb1 doc: fix typo in ganesha-config manpage Daniel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] nss_getpwnam: name 't...@my.dom@localdomain' does not map into domain 'nix.my.dom'
It's probably a good idea to add the build options to --version output, or something. That way we can ask for it in these types of situations. I've added a card to the wishlist for this. Daniel On Tue, Mar 20, 2018 at 9:39 AM, TomK wrote: > On 3/19/2018 9:54 AM, Frank Filz wrote: >>> >>> Solved. >>> >>> Here's the solution in case it can help someone else. >>> >>> To get a certain feature in NFS Ganesha, I had to compile the V2.6 >>> release from source. When configuring to compile, idmapd support got >>> disabled since packages were missing: >>> >>> libnfsidmap-devel-0.25-17.el7.x86_64 >>> >>> Installed the above package and recompiled with nfsidmap support enabled >>> and this issue went away. Users now show up properly off the NFS mount >>> on clients. >> >> >> Oh, well that was a simple fix :-) >> >> I wonder if we could make changes in our cmake files to make it easier to >> see when stuff got left out due to missing packages? I've been caught out >> myself. >> >> Frank >> > Yep, sure was an easy fix. > > Wouldn't mind seeing that. Maybe even a way to find out what options went > into compiling packages for each distro. > > > -- > Cheers, > Tom K. > - > > Living on earth is expensive, but it includes a free trip around the sun. > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
