OK, I have a memory/ transfer speed question as well.
My 4000 is transfering data really slow. I transfered 50MB in 60 seconds in last nights test.
Some will argue that I'ts because I am using disks that are "too large" in a raid 5, but everything else is working fine, and I broken and rebuild the array fine, etc.
01/16/2007 23:03:21 Command: debug memory
Total System Physical Memory: 268435456
File System Memory Allocated: 179972592
Memory To be Written: 8304
Memory On Loan: 0
Loan Count: 0
Heap Memory: 159009040
Memory In Use: 156224112
Objects Allocated: 25
Communication Memory Allocated: 2059232
Memory In Use: 467604
SDB Non-Volatile Memory Allocated: 65536
Memory In Use: 16168
Handles Allocated:4679
Handles In Use: 362
SDB Volatile Memory Allocated: 98304
Memory In Use: 330
Handles Allocated: 11705
Handles In Use: 12
System has been configured!
Perhaps the transfer speeds are totally unrelated to memory, but I have see other 'debug memory' listings and the file system memory is only 20MB lower than the total system memory. Can/should I change this?
It would be nice to see some wiki entries on these values or the debug commands in general. for example, I see these values change durring large transfers
from the server:
Memory To be Written: 24912
Memory On Loan: 8304
Loan Count: 1
...but I don't know what it means or if it shows any problems.
here is more of what I know not.
cache size = 65526KB
number of worker threads = 64
current/max device total i/o count = 95/999
current/max device read i/o count = 60/130
current/max device write i/o count = 34/987
current/max work queue size = 232/1437
cache lookaside read hit ratio = 0%
cache read hit ratio = 7%
array index 0 (device 0x80060000):
stripe size = 64KB
current/max total i/o count = 331/1439
current/max read i/o count = 1/9
current/max write i/o count = 329/1437
active context = 0x25F9030
active context = 0x25F9098
active context = 0x25F9168
active context = 0x25F919C
active context = 0x25F926C
01/16/2007 23:21:27 Command: debug heap
Summary of Heap Pool Memory:
Total Physical Memory:268435456 Effective:264896464 Initial Heap:2097152 Maximum allocation size:8252
Startup Buffer:8388608 Startup required:108928944 Minimum Bio Bufs:63 Actual Bio Bufs:21672
Current Heap Allocs: 28 BioBuf Allocs: 1 Heap Dry: 0 Failed Allocs: 0 Untouched Heap:2065312
#defines: DLEVEL(0), Roundup_BigAllocs(>7168 to 8252),
Size_Queues, !Statistics, Adjust_SizeQs every 120 secs)
ASSERT_DEBUG, ASSERT_LEVEL 0
Block List: REGION Header Address Len REGION Header Address Len
Heap: 0x003E803C : 0x0685B70C - 159009008 Heap: 0x0001800C : 0x0009FFFC - 0
Free List: ADDRESS Length ADDRESS Length ADDRESS Length
0x0F6510CC - 336 0x0FD4D3CC - 2073616
Heap has been validated and no problems were found.
Summary of Queues:
QUEUE MIN BLOCKS(PER) TOTAL FREE ALLOCD TRIM
SizeQ_32 480 + 0 x 0 480 463 17 0 Valid.
SizeQ_64 640 + 0 x 0 640 607 33 0 Valid.
SizeQ_160 2048 + 0 x 0 2048 1996 52 0 Valid.
SizeQ_256 128 + 0 x 0 128 128 0 0 Valid.
SizeQ_512 256 + 0 x 0 256 238 18 0 Valid.
SizeQ_1024 64 + 0 x 0 64 57 7 0 Valid.
SizeQ Adjust Timer inactive.
Block Lists:REGON Header Address Len REGION Header Address Len
SizeQ_32 Heap: 0x0FFF87EC : 0x0FFF87FC - 30704
SizeQ_64 Heap: 0x0FFE97BC : 0x0FFE97CC - 61424
SizeQ_160 Heap: 0x0FF8978C : 0x0FF8979C - 393200
SizeQ_256 Heap: 0x0FF8075C : 0x0FF8076C - 36848
SizeQ_512 Heap: 0x0FF5E72C : 0x0FF5E73C - 139248
SizeQ_1024 Heap: 0x0FF4DEFC : 0x0FF4DF0C - 67568
Total Memory in Queues and Heap currently available: 697664
=========================
01/16/2007 23:40:32 Command: debug ffs
mounts: 1 unmounts: 0
getattrs: 879 roots: 4572
statfs: 1 fhtovps: 0
vptofhs: 0 inits: 1
lookups: 40804 opens: 161
closes: 161 strategys: 0
access: 179 reads: 322
readdirs: 0 locks: 903450
unlocks: 885305 inactives: 1326
reclaims: 663 writes: 0
Vnodes: Min: 8192 Max: 20480 Current: 8192 Free: 8164
File Descriptors: Max: 16384 Current: 15
Does anyone see something unusual here? I have no experience with snap servers other than this one.
Thanks!