Originally posted by perpetually high
View Post
Announcement
Collapse
No announcement yet.
The Sandy Bridge Core i7 3960X Benchmarked Against Today's Six-Core / 12 Thread AMD/Intel CPUs
Collapse
X
-
Originally posted by atomsymbolI agree that mitigations=off is good for notebook&desktop machines (assuming the user ensures that the machine never runs malicious code).
- Likes 1
Leave a comment:
-
Originally posted by coder View PostThanks. Does PTS log raw dmidecode output?
- Likes 1
Leave a comment:
-
Originally posted by atomsymbol- If a machine feels unresponsive then the user should primarily take a look at how many tasks are competing for the available hardware threads and should check whether the peak number of running tasks exceeds the number of HW threads. A desktop environment indicator such as xfce4-systemload-plugin can help identify cases of high CPU utilization. The scheduling priority of build jobs (Makefiles, etc) should be kept lower than the scheduling priority of GUI applications.
- Likes 1
Leave a comment:
-
Originally posted by coder View PostWhat's the memory configuration of the 3960X - did you use dual-channel or quad-channel? What speed?
Also, the article doesn't mention that the 3 newer systems used a NVMe SSD, while the Sandy Bridge used SATA. That said, the NVMe drive was one of the slower models out there, but IMO it should be noted.
Thanks.
Leave a comment:
-
Originally posted by coder View PostWhat's the memory configuration of the 3960X - did you use dual-channel or quad-channel? What speed?
Also, the article doesn't mention that the 3 newer systems used a NVMe SSD, while the Sandy Bridge used SATA. That said, the NVMe drive was one of the slower models out there, but IMO it should be noted.
Thanks.
Leave a comment:
-
Originally posted by phoronix View PostPhoronix: The Sandy Bridge Core i7 3960X Benchmarked Against Today's Six-Core / 12 Thread AMD/Intel CPUs
Also, the article doesn't mention that the 3 newer systems used a NVMe SSD, while the Sandy Bridge used SATA. That said, the NVMe drive was one of the slower models out there, but IMO it should be noted.
Thanks.
Leave a comment:
-
Originally posted by atomsymbol
It isn't inverted. Build tasks aren't interactive applications and so giving them higher priority seems contradictory to me. I don't want build tasks to run with higher priority than Chrome/Firefox for example.
Leave a comment:
-
Originally posted by yokem55 View PostAnd I generally agree with you - But you do have to be pretty mindful of where the code you are running is coming from. Ie making sure all your repo's are signed, don't install random .deb's, tarballs, appimages, etc. Even building electron apps from source can be risky because of the security shit-show that npm is. The same problem with apps installed with pip/pypi. Also you have to cross your fingers that this stuff never becomes easily exploitable via javascript in your browser...
What brings me peace at home is that a router gives a good line of defense. I only have one port open and that's for OpenVPN via the pi-hole (using PiVPN software). If for example there's an exploit in OpenVPN, there's a clear entry for an attacker on my IP. Any other interface I can hopefully safely assume is inaccessible. I imagine if you have a webserver/ssh/etc on, even more points of entry. Shell shock, Heartbleed, I'm sure more will come out.
The pi-hole is nice because you see an overview of your network requests across all your devices on the network. So if a Windows PC on the network was phoning home, you'd know right away. In terms of software, I get all my apps from official websites, git and package repositories but like you said, huge trust system there.
The web browser is definitely the easiest point of entry. I'm using Firefox + the pi-hole to block ads/malicious domains + DuckDuckGo Privacy Essentials. I should probably go a step further and be responsible and install the NoScript extension. Firefox also came out with a Firefox Private Network addon the other day which is pretty cool.
- Likes 1
Leave a comment:
Leave a comment: