From 4442abc3c102ad75badef5c56243ccf0949cc831 Mon Sep 17 00:00:00 2001 From: Jeffrey Altman Date: Thu, 17 May 2007 17:19:03 +0000 Subject: [PATCH] DEVEL15-windows-notes-20070517 notes for 1.5.20 --- doc/txt/winnotes/afs-changes-since-1.2.txt | 34 +++++ doc/txt/winnotes/afs-issues.txt | 14 +- doc/txt/winnotes/performance.txt | 154 ++++++++++++--------- 3 files changed, 136 insertions(+), 66 deletions(-) diff --git a/doc/txt/winnotes/afs-changes-since-1.2.txt b/doc/txt/winnotes/afs-changes-since-1.2.txt index 2b1a01d3c..bd67ba1a8 100644 --- a/doc/txt/winnotes/afs-changes-since-1.2.txt +++ b/doc/txt/winnotes/afs-changes-since-1.2.txt @@ -1,3 +1,37 @@ +Since 1.5.19 + * fix install path of IBM Quick Start Guide when installed by + the Wix installer + + * fix the client so that it can write into directories with + only 'li' permissions. + + * fix installation of 32-bit Shell Extension for 64-bit systems. + Install it under its own HKCR keys. + + * modify the wix installer to remove and upgrade install packages + with the same version number. + + * when flushing volume location data every two hours or in + response to "fs checkvolumes", also flush the mount point + links in order to force their re-evaluation. + + * aklog was copying an uninitialized buffer as part of the + foreign cell automatic pts registration + + * when obtaining directory listings, check for read permission + on the directory. If read permission does not exist, fake the + status information for the directory entries. This improves + performance, prevents the client from pounding the file server, + and prevents leakage of cached status information. + + * "fs getcacheparms" output was incorrect. + + * NetIdMgr AFS Provider should only automatically add token + acquisition for cell foo.com if the realm of the cell matches + the realm of the identity. + + * Fix a null pointer dereference in cm_MergeStatus() + Since 1.5.18 * network identity manager provider: diff --git a/doc/txt/winnotes/afs-issues.txt b/doc/txt/winnotes/afs-issues.txt index 58084769b..f07b7c27e 100644 --- a/doc/txt/winnotes/afs-issues.txt +++ b/doc/txt/winnotes/afs-issues.txt @@ -1,4 +1,4 @@ -This file is a rough list of known issues with the 1.5.15 release of OpenAFS +This file is a rough list of known issues with the 1.5.20 release of OpenAFS on Windows. This list is not complete. There are probably other issues which can be found in the RT database or on the mailing list. @@ -121,4 +121,14 @@ List of unfunded projects: four simultaneous requests to a single server to be processed at a time for a single user 27. Support the Vista User Account Control (UAC) interface - \ No newline at end of file + + + + + + + + + + + diff --git a/doc/txt/winnotes/performance.txt b/doc/txt/winnotes/performance.txt index be370b681..856639288 100644 --- a/doc/txt/winnotes/performance.txt +++ b/doc/txt/winnotes/performance.txt @@ -1,64 +1,90 @@ -argos.mit.edu with 1.3.73 client -171,194,368 byte file. "fs flush" before each command - -200mb cache; No MaxMTU - write/crypt 2.793 MB/sec - read/crypt 2.897 MB/sec - - write/clear 7.123 MB/sec - read/clear 5.991 MB/sec - -1.2.10(skyrope) - write/crypt: 1.836 MB/sec - read/crypt: 1.497 MB/sec - - write/clear: 2.927 MB/sec - read/clear: 2.065 MB/sec - - - 1.2.10 1.3.73 improvement - ------------ ------------ ----------- -write/crypt 1.836 MB/sec 2.793 MB/sec 52.1% -read/crypt 1.497 MB/sec 2.897 MB/sec 93.5% - -write/clear 2.927 MB/sec 7.123 MB/sec 143.4% -read/clear 2.065 MB/sec 5.991 MB/sec 190.1% - - - -mitz@ANDREW.CMU.EDU tested the 1.3.73 client on his machine -against his cell copying a 367181824 byte file. "fs flush" -was run prior to each command. - - -Default MaxMTU; Default cache - write/crypt: 4.158 MB/sec - read/crypt: 5.730 MB/sec - - write/clear: 4.537 MB/sec - read/clear: 16.762 MB/sec - -Changing the cache size made no difference - -No MaxMTU; 400MB cache - write/crypt: 4.863 MB/sec - read/crypt: 6.083 MB/sec - - write/clear: 14.286 MB/sec - read/clear: 16.257 MB/sec - -From Andrew Linux with 1.2.10 on the same machine: - write/crypt: 5.358 MB/sec - read/crypt: 12.855 MB/sec - - write/crypt 18.040 MB/sec (unique file names) - read/crypt 23.160 MB/sec (unique file names) - - write/clear: 16.401 MB/sec - read/clear: 25.192 MB/sec - - - - - - +argos.mit.edu with 1.3.73 client +171,194,368 byte file. "fs flush" before each command + +200mb cache; No MaxMTU + write/crypt 2.793 MB/sec + read/crypt 2.897 MB/sec + + write/clear 7.123 MB/sec + read/clear 5.991 MB/sec + +1.2.10(skyrope) + write/crypt: 1.836 MB/sec + read/crypt: 1.497 MB/sec + + write/clear: 2.927 MB/sec + read/clear: 2.065 MB/sec + + + 1.2.10 1.3.73 improvement + ------------ ------------ ----------- +write/crypt 1.836 MB/sec 2.793 MB/sec 52.1% +read/crypt 1.497 MB/sec 2.897 MB/sec 93.5% + +write/clear 2.927 MB/sec 7.123 MB/sec 143.4% +read/clear 2.065 MB/sec 5.991 MB/sec 190.1% + + +lxiv.mit.edu with 1.5.1407 client +171,194,368 byte file. "fs flush" before each command +1260 MaxMTU + +write/crypt 2.050 MB/sec +read/crypt 2.596 MB/sec + +write/clear 2.574 MB/sec +read/clear 7.371 MB/sec + +No MaxMTU + + 1.5.14 1.5.1408 change + -------------- ------------- ---------- + +write/crypt/flush 3.146 MB/sec 2.659 MB/sec -15.5% +read/crypt/noflush 2.951 MB/sec 54.421 MB/sec +1844.2% +read/crypt/flush 2.946 MB/sec 2.925 MB/sec - 0.7% + +write/clear/flush 8.221 MB/sec 5.542 MB/sec -32.6% +read/clear/noflush 10.493 MB/sec 54.421 MB/sec +518.6% +read/clear/flush 10.385 MB/sec 10.741 MB/sec +3.4% + + + + + +mitz@ANDREW.CMU.EDU tested the 1.3.73 client on his machine +against his cell copying a 367181824 byte file. "fs flush" +was run prior to each command. + + +Default MaxMTU; Default cache + write/crypt: 4.158 MB/sec + read/crypt: 5.730 MB/sec + + write/clear: 4.537 MB/sec + read/clear: 16.762 MB/sec + +Changing the cache size made no difference + +No MaxMTU; 400MB cache + write/crypt: 4.863 MB/sec + read/crypt: 6.083 MB/sec + + write/clear: 14.286 MB/sec + read/clear: 16.257 MB/sec + +From Andrew Linux with 1.2.10 on the same machine: + write/crypt: 5.358 MB/sec + read/crypt: 12.855 MB/sec + + write/crypt 18.040 MB/sec (unique file names) + read/crypt 23.160 MB/sec (unique file names) + + write/clear: 16.401 MB/sec + read/clear: 25.192 MB/sec + + + + + + -- 2.39.5