today's leftovers
-
Summing Up The AMD EPYC 7742 2P Performance In One Graphic
If you didn't have a chance since last night to check out our benchmarks of the AMD EPYC 7742 and EPYC 7502 Linux performance, I certainly encourage you to do so. Even if you aren't a server enthusiast, it's incredible to see the engineering achievement of AMD with Zen 2 and how the race is certainly back on in the CPU space. If you are short on time, here's the quick summary of our initial AMD EPYC 7002 benchmark results.
As all independent reviewers seem to be in consensus, the EPYC 7002 series is a godsend for just about everyone, sans Intel. The EPYC 7002 line-up provides the most competitive option against Intel we've seen in the server space in many years if not ever, customers have these lower-cost CPUs that actually perform better and more power efficient in a majority of real-world workloads, and Rome further benefits consumers by reigniting Intel's engine and they will certainly need to respond in some manner by either (much) better pricing or some card up their sleeves.
-
How Can AMD EPYC "Rome" 7002 Series Be Even Better? Open-Source BIOS / Coreboot
By now you've likely seen the fantastic performance out of AMD's new "Rome" 7002 series processors. The performance is phenomenal and generally blowing well past Intel's Xeon Cascade Lake processors. So that's all good and it can get even better outside of performance: I asked AMD about the prospects of Coreboot / open-source BIOS support and got a surprising response.
At an event in Austin last month when AMD was talking up Rome, when they weren't talking about the new server CPU's performance potential they were often mentioning the chip's security. That set the stage for bringing up open-source support and Coreboot support without coming across as just an open-source zealot/nerd question. After all, if their lower-level bits were (again) open-source it would ensure a more auditable boot process and ensuring the integrity of their Platform Security Processor (PSP) and the like, which in this day and age is important and trying to ensure no nefarious back-doors to the system. Companies like Facebook and Google are also genuinely interested in this open-source functionality with their work on the likes of Coreboot and LinuxBoot.
-
Curbing Harassment with User Empowerment
Typically, we want to communicate with strangers online, so this should be possible by default. But if we are being actively harassed, we can assume that further messages from strangers are unsafe, and switch our account to “safety mode”–rejecting messages, invites and other interactions from strangers. We can rely on our trusted contacts for help and support, including passing on well-wishes from strangers.
At-risk individuals might choose to start their account in safety mode.
Trusted caretakers might maintain lists of bad actors, but trusting a caretaker should require very careful consideration: What is their governance model? What is their appeals process? Do they leak information about list recipients?
-
Python and public APIs
In theory, the public API of a Python standard library module is fully specified as part of its documentation, but in practice it may not be quite so clear cut. There are other ways to specify the names in a module that are meant to be public, and there are naming conventions for things that should not be public (e.g. the name starts with an underscore), but there is no real consistency in how those are used throughout the standard library. A mid-July discussion on the python-dev mailing list considered the problem and some possible solutions; the main outcome seems to be interest in making the rules more explicit.
It should be noted that the Python language does not enforce any access restrictions at all; any program that can import a module can access any top-level name defined in it. All of the "rules" that govern access restrictions are simply conventions, though they are meant to delineate things that can be changed by a module maintainer without going through the usual deprecation cycle. A big part of the public API is effectively a list of names that the module maintainer promises not to change without a good deal of warning (at least two full development cycles).
- Login or register to post comments
- Printer-friendly version
- 2112 reads
- PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is releasedAfter three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. |
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future TechThe metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. |
today's howtos
|
Recent comments
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago