Those benchmarks are generally in wine.
Wine is a program that basically reimplements windows in linux so to speak, so there's some overhead.
Native stuff in many cases run faster than windows.
Who needs Winblows?
Most bottlenecks on linux with games or crossplatform software come from windows devs doing the minimal amound of work to do a linux port. Proper native software runs about the same when there's no other CPU hogs around, which ends up being faster because on Linux you're usually not running that extra security crap.
It's complicated, it's not like Linux will make your CPU slower at all. If anything the scheduler is top notch. But if something has less attention (like a neglected linux port) or runs through a compatibility layer then it could easily be slower.
Basically:
>Games could be slower depending on driver and port quality
>Graphics-related stuff might be slower (drivers etc) but AMD might actually be faster desu
>Computation speed will be equal or faster
>IO-related workflows or ones which create a lot of processes (copying files, reading lots of small files, compiling) will be MUCH faster
Take into account if said benchmark was done on wine or native. Basically every modern valve game runs better on linux than it does on windows because they put equal effort in both. And by modern I mean not L4D2 since it's unmaintained and it was their test project
Most of the performance loss going from Windows -> Linux comes from D3D->OpenGL, or D3D->Vulkan.
This is improving but the only real solution is for developers to start supporting standards instead of using D3D.
Games and benchmarks that are optimized for the native APIs tend to perform about the same or better depending on your hardware.