Hi,
Just like in the title, and the accompanying graphs, shorty after boot, the wired memory goes way down, the services go way up to almost all of my memory and stay there.
If I transfer a large file immediately after boot, before the wired memory goes down, I get very consistent, steady, normal network usage in windows task manager and very acceptable transfer speeds. But after the wired memory goes down and the services reach 20 gigs, I get very strange saw-tooth networking use, and slower transfer speeds.
(see both windows task manager screenshots)
TrueNas is the most up to date version (12.0-U2.1) and it's running inside a proxmox hypervisor. There are no VMs or plugins inside truenas itself. The drives are on a LSI HBA passedthrough'ed to the TrueNas VM, and so is the Chelsio 10gig network card, no virtIO anywhere except boot drive.
One thing I can think of is that the RAM isn't acutally ECC like trunas claims, it's regular DDR4, but I assume that's something to do with proxmox, and I don't see how that would cause weird utilization.
I tried disabling services one by one to see if I got some ram back but no. I only have 3 services running anyway, SMART, SMB and SSH
Just like in the title, and the accompanying graphs, shorty after boot, the wired memory goes way down, the services go way up to almost all of my memory and stay there.
If I transfer a large file immediately after boot, before the wired memory goes down, I get very consistent, steady, normal network usage in windows task manager and very acceptable transfer speeds. But after the wired memory goes down and the services reach 20 gigs, I get very strange saw-tooth networking use, and slower transfer speeds.
(see both windows task manager screenshots)
TrueNas is the most up to date version (12.0-U2.1) and it's running inside a proxmox hypervisor. There are no VMs or plugins inside truenas itself. The drives are on a LSI HBA passedthrough'ed to the TrueNas VM, and so is the Chelsio 10gig network card, no virtIO anywhere except boot drive.
One thing I can think of is that the RAM isn't acutally ECC like trunas claims, it's regular DDR4, but I assume that's something to do with proxmox, and I don't see how that would cause weird utilization.
I tried disabling services one by one to see if I got some ram back but no. I only have 3 services running anyway, SMART, SMB and SSH