[Feat] AppImage improvements. #150

Open
opened 2024-04-14 13:02:58 +02:00 by Samueru · 0 comments

Is there an existing issue for this?

  • I have searched the existing issues

What feature are you suggesting?

This is two requests for suyu, the first request is to release a x86-64 v3 appimage. As that carries a small performance improvement, specially in the low fps which on my own tests had a noticeable impact, there is also these benchmarks back in the yuzu days:

https://www.reddit.com/r/yuzu/comments/13untvp/if_you_want_to_gain_a_little_more_performance/

That is done by changing the -DCMAKE_CXX_FLAGS="-march=x86-64-v2" \ to -DCMAKE_CXX_FLAGS="-march=x86-64-v3" \ line in the ci linux docker.sh script.

Now this means that two appimages would have to be released, as x86-64-v3 is not compatible with cpus older than haswell.

(Also I think you have to add -O3 in the flags as well, otherwise suyu gets build with -O2 by default instead).

The other request is to use go-appimage for appimagetool, which is made by probonopd (the creator of appimage): https://github.com/probonopd/go-appimage.

The advantage this has is that it is compatible with fusermount3, as today distros are starting to not install fuse2 by default which is needed by appimage built with the older appimagetool. Also this uses zstd compression by default which makes the appimage slightly smaller, usage is about the same as with the older appimage tool, for example once the suyu.AppDir is made this is how the tool is used:

ARCH=x86_64 VERSION=$(./appimagetool -v | grep -o '[[:digit:]]*') ./appimagetool-823-x86_64.AppImage -s ./suyu.AppDir

Why would this feature be useful?

These features improve performance and compatibility of suyu.

### Is there an existing issue for this? - [x] I have searched the existing issues ### What feature are you suggesting? This is two requests for suyu, the first request is to release a x86-64 v3 appimage. As that carries a small performance improvement, specially in the low fps which on my own tests had a noticeable impact, there is also these benchmarks back in the yuzu days: https://www.reddit.com/r/yuzu/comments/13untvp/if_you_want_to_gain_a_little_more_performance/ That is done by changing the `-DCMAKE_CXX_FLAGS="-march=x86-64-v2" \` to `-DCMAKE_CXX_FLAGS="-march=x86-64-v3" \` line in the ci linux docker.sh script. Now this means that two appimages would have to be released, as x86-64-v3 is not compatible with cpus older than haswell. (Also I think you have to add -O3 in the flags as well, otherwise suyu gets build with -O2 by default instead). The other request is to use go-appimage for appimagetool, which is made by probonopd (the creator of appimage): https://github.com/probonopd/go-appimage. The advantage this has is that it is compatible with fusermount3, as today distros are starting to not install fuse2 by default which is needed by appimage built with the older appimagetool. Also this uses zstd compression by default which makes the appimage slightly smaller, usage is about the same as with the older appimage tool, for example once the suyu.AppDir is made this is how the tool is used: `ARCH=x86_64 VERSION=$(./appimagetool -v | grep -o '[[:digit:]]*') ./appimagetool-823-x86_64.AppImage -s ./suyu.AppDir` ### Why would this feature be useful? These features improve performance and compatibility of suyu.
Samueru added the
enhancement
label 2024-04-14 13:02:58 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: suyu/suyu#150
No description provided.