Better Wine Benchmarking This Summer For Windows Programs On Linux

[ermo]

Got an FX-8350 w/a HD 7970 GHz Ed. which is chomping at the bit to get to run some Wine benchmarks, so this sounds excellent!

I'm pretty excited about how the DX9 and DX11 over Vulkan stuff is going to pan out now that my GPU supports Vulkan via RADV. It'll be interesting to see if the Vulkan backend will over time allow DirectX titles to have less overhead via Wine than having going through AMD's Windows drivers. Should that scenario ever come to pass, it'll be quite hilarious!

[Michael]

Michael

Very good

However can put poll asking about which titles like see tested

It's more along the lines of what games can be automated nicely... And for my purposes, what games I have access to.

[pinguinpc]

Michael

Very good

However can put poll asking about which titles like see tested

[Flaburgan]

Thank you very much for taking care of wine. I run most of my game with it, this work will be very valuable.

[Michael]

Michael you could use the Lutris wine and winde-staging builds. They update pretty quickly after a new release

But this repo does just new 'releases'? So every 2 weeks? I was hoping for a PPA that would be automatically pushing out new builds nightly or at least like weekly, certainly would help in catching regressions quicker.

[aaahaaap]

Michael you could use the Lutris wine and winde-staging builds. They update pretty quickly after a new release

[muncrief]

The USE_WINE module at this point respects WINEPREFIX. Is there any other useful Wine variable to pay attention to?

I currently place the following default environment variables in ~/.profile:

# Set Wine Manager Variables
export WINEMGR_DATA_DIR=`echo ~/.winemgr`
export WINEMGR_MENU_ROOT=`echo ~`
export WINEMGR_MENU_REFRESH="xfce4-panel -r"

# Set Default Wine Paths
export WINEVERPATH=`echo $WINEMGR_DATA_DIR/wine_dflt`
export PATH=$WINEVERPATH/bin:$PATH
export WINESERVER=$WINEVERPATH/bin/wineserver
export WINELOADER=$WINEVERPATH/bin/wine
export WINEDLLPATH=$WINEVERPATH/lib/wine/fakedlls
export LD_LIBRARY_PATH="$WINEVERPATH/lib:$LD_LIBRARY_PATH"

# Set Wine Staging Realtime Priority
export STAGING_RT_PRIORITY_SERVER=95
export STAGING_RT_PRIORITY_BASE=95

And then each Wine version has it's own custom environment script. Here's an example:

#!/bin/bash
export WINEVERPATH=/opt/wine-staging-3.9
export PATH=$WINEVERPATH/bin:$PATH
export WINESERVER=$WINEVERPATH/bin/wineserver
export WINELOADER=$WINEVERPATH/bin/wine
export WINEDLLPATH=$WINEVERPATH/lib/wine/fakedlls
export LD_LIBRARY_PATH="$WINEVERPATH/lib:$LD_LIBRARY_PATH"

This enables me to run multiple Wine versions and programs within their own environment. But it would be near impossible to explicitly take into account custom setups like mine. That's why I'd recommend some facility to execute user setup scripts before invoking a benchmark. And thank you for your quick response!

[muncrief]

Sometimes the spam filter sends stuff into mod queue, it's up there now.

Thank you Michael. I was aware of the filter and just wanted to let someone know. Thank you for taking care of the issue so quickly, I just didn't want it to get lost in the bucket

[Michael]

I run Wine with my own Wine Manager script because there isn't any other viable way for me to run multiple simultaneous installations. I know there are things like PlayOnLinux but they're very restrictive and don't integrate Wine programs into the XDG menu. My script solves those problems, and allows you to put Wine programs in the menu with whatever hierarchy you wish. The only restriction is that they appear under "Wine." For example, I have all games under "Wine->Games->Steam64 and Wine->Games->Steam32" etc. And all multimedia programs under "Wine->Multimedia->xxx", all graphics programs under "Wine->Graphics->xxx" etc.

However my Wine Manager doesn't automatically install different Wine versions, or Wine programs. You have to install different Wine versions by hand, and with Manjaro that means you have to compile them manually. You also have to open a command prompt and type "winemgr install -b <bottle name>" which invokes the appropriate Wine environment in the shell. And then you have to manually install the program. So for most people things like PlayOnLinux are unfortunately the only way to go.

In any case I hope the Wine benchmark suite will allow you to set up your own environment and point to whatever Wine installation you want. I have a single environment script for each version that sets the appropriate variables and if I could execute it from the benchmark program that would be awesome! I'd love to be able to benchmark Wine programs.

The USE_WINE module at this point respects WINEPREFIX. Is there any other useful Wine variable to pay attention to?

[lectrode]

Very cool stuff. Looking forward to more regular WINE vs Windows benchmarks.

Unfortunately the Wine daily build PPA no longer is maintained nor does there seem to be any other daily/bi-daily package repositories for Ubuntu or other tier-one Linux distributions that I am aware of... If anyone has any ideas, feel free to share so then I could also be providing these automated routine Wine benchmarks. I'd much prefer having a public package archive so that others could pull from the same binaries for comparison/reproducing and to eliminate any possible questions by others over the Wine build configuration, etc.

If you want to use Arch or an Arch derivative, the wine-git and wine-staging-git packages in the AUR might be useful for this. Granted, you'd still be compiling it, but at least it's a publicly available build configuration with version history.