Language Selection

English French German Italian Portuguese Spanish

GeForce GTX 650 vs. GTX 1650 Performance For Linux Gaming, Performance-Per-Watt

Filed under
Graphics/Benchmarks
Gaming

The latest in our benchmarking with the new GeForce GTX 1650 is some "fun" tests seeing how its performance compares to that of the GeForce GTX 650 Kepler. Various OpenGL and Vulkan Linux gaming tests were carried out as well as some compute tests and throughout monitoring the AC power consumption to yield the performance-per-Watt metrics.

The GeForce GTX 650 Kepler graphics card launched nearly seven years ago already with its 40nm GK107 GPU that provided 384 CUDA cores, 1058MHz core clock speed, and 1GB of GDDR5 video memory. The GTX 650 has a 64 Watt TDP but came with a 6-pin PCIe power connector. The GTX 650 / Kepler is the last generation currently supported by the mainline Linux driver and also the oldest NVIDIA hardware with Vulkan driver coverage, making this comparison particularly interesting.

The GeForce GTX 1650 meanwhile with its 12nm TU117 GPU has 896 CUDA cores, 1485MHz base clock speed, 1665MHz boost clock speed, and 4GB of GDDR5 video memory. The GeForce GTX 1650 has a 75 Watt TDP without the need for any external PCIe power connection.

Read more

More in Tux Machines

today's howtos

KDE Frameworks 5.61, Applications 19.08 in FreeBSD

Recent releases were KDE Frameworks 5.61 and KDE Applications 19.08. These have both landed in the official FreeBSD ports tree, after Tobias did most of the work and I pushed the big red button. Your FreeBSD machine will need to be following current ports – not the quarterly release branches, since we don’t backport to those. All the modern bits have arrived, maintaining the KDE-FreeBSD team’s commitment to up-to-date software for the FreeBSD desktop. The one thing we’re currently lagging on is Qt 5.13. There’s a FreeBSD problem report tracking that update. Read more

Dev branch moving towards Qt 6

As you know, Qt 5.14 will be branched pretty soon. After that I would expect that most new development work would start to be aimed towards Qt 6. As it looks right now, 5.15 will be a smaller release where we polish what we have in 5.14, and prepare some things for Qt 6. To reflect that and help us all understand that the development focus is now towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6 back into dev). We can then either create a 5.15 branch at the same time, or slightly later, once 5.14 has stabilised a bit more (e.g. after the beta or RC). Read more Also: Qt's Development Branch To Begin Forming Qt 6

Today in Techrights