I’ve noticed that process
SpokesUpdateService is promoted to the top of my Memory list. Here an example which I captured today (just 24hrs after my last reboot) but on the other day I’ve seen 2.4 GB wasted:
It turned out to be part of PlantronicsHub software. I will disable to for a while an see how it will behave.
My current home server which I use many for virtualisation, serving also some net services is reaching memory and disk-space limits. I named this server Wieloryb which in Polish means The Whale.
So far I have:
Lenovo M910t server
64 GB RAM
1x 1 TB SATA HDD (3.5”) – configured root ZFS Pool (RAID1)
3x 2 TB SATA HDD (3.5”) – storage1 ZFS Pool (RAID5)
1x 254 GB SATA SDD (2.5”) – storage2 ZFS Pool
1x 254 GB (M.2) – cache for ZFS pools (Cache and L2ARC). I know, L2ARC should be mirrored but I decided that I will take the risk
PCI-e 4x SATA board to provide 4 + 4 SATA connectors (M’board + PCI-e board)
The three 2 TB HDD disks and 254 GB SSD disks are stored in Icy Dock 4-disks cage. The disk cage allows to connect all 4 disks through 4 SATA connectors
The disk cage is powered by an external PSU (as the PC’s PSU is not strong enough)
On-demand backups are made to a 4 TB SATA HDD using i-tec USB HDD dock
Remote management is possible thanks to Belkin Net KVM
Sending critical alarms via SMSes as well as forwarding of SMSes from my old mobile SIM are done thanks to Nokia USB stick and Gammu software
And finally – a small UPS
Picture of the lab
For greater flexibility and separation between different tasks I decided to use Proxmox as virtualisation manager. No issues with that: it does what it should, small issues can be justified by a very attractive price (0 USD…).
Another embarrassing problem with my MBP: when scrolling in e.g. Chrome, Safari or actually – any other window, there is annoying lag. When you scroll continuously, it’s more or less fine, but when you pause to read and then want to scroll, it stutters.
After a bit checking here and there, it turned out that if I increased keyboard backlight timeout from 5 seconds to 1 minute, the problem has been worked around!