Language Selection

English French German Italian Portuguese Spanish

GNOME Shell + Mutter 3.31.4 Deliver Desktop Performance Improvements

Filed under
GNOME

While released too late for making it into GNOME 3.31.4 proper as the newest GNOME 3.32 development release, out today are GNOME Shell 3.31.4 and Mutter 3.31.4 and both of these components offer up performance fixes/improvements.

GNOME Shell 3.31.4 improves the icon grid performance, which is for a bug opened for nearly one year about high CPU usage when scrolling the app grid. This was reported by Canonical's Daniel van Vugt and even for a Core i7 Kabylake desktop CPU the app grid scrolling introduced high CPU overhead while now has the necessary fixes in place.

Read more

Also: Librsvg is almost rustified now

More in Tux Machines

Compact Jetson TX2 computer has eight USB 3.0 ports

Aaeon’s rugged “Boxer-8150AI” computer runs Linux on a Jetson TX2 module and features 2x HDMI ports and 8x USB 3.0 ports for hooking up cameras for on-site edge AI analytics. Like the quad-GbE Boxer-8120AI, the Boxer-8150AI uses an Nvidia Jetson TX2 module and its CUDA-enabled AI libraries to analyze visual information from connected cameras. In this case, the cameras don’t run over Ethernet, but USB 3.0. Like the Boxer-8120AI and Aaeon’s stripped down Boxer-8110AI spinoff, this is a fanless, rugged, Linux-driven device with a compact form factor, in this case measuring 153 x 101 x 45mm. Read more

Android Leftovers

Android Low-Memory Killer--In or Out?

One of the jobs of the Linux kernel—and all operating system kernels—is to manage the resources available to the system. When those resources get used up, what should it do? If the resource is RAM, there's not much choice. It's not feasible to take over the behavior of any piece of user software, understand what that software does, and make it more memory-efficient. Instead, the kernel has very little choice but to try to identify the software that is most responsible for using up the system's RAM and kill that process. The official kernel does this with its OOM (out-of-memory) killer. But, Linux descendants like Android want a little more—they want to perform a similar form of garbage collection, but while the system is still fully responsive. They want a low-memory killer that doesn't wait until the last possible moment to terminate an app. The unspoken assumption is that phone apps are not so likely to run crucial systems like heart-lung machines or nuclear fusion reactors, so one running process (more or less) doesn't really matter on an Android machine. Read more

today's leftovers