Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance Degradation from 1.0.2 to 1.0.3 on Linux #32

Open
csfalcione opened this issue Sep 20, 2019 · 23 comments
Open

Performance Degradation from 1.0.2 to 1.0.3 on Linux #32

csfalcione opened this issue Sep 20, 2019 · 23 comments

Comments

@csfalcione
Copy link

@csfalcione csfalcione commented Sep 20, 2019

Tested the AppImages on Linux Mint 19.2 with a 6600K, GTX 1070 (with the 430 proprietary driver), and kernel 5.0.0. Used a wired DS4. In 1.0.3, there is a slight stutter upon every button press, but at least a second long freeze when the triggers are pressed. Also, the framerate seems to be lower overall. In 1.0.2, streaming is buttery smooth (but sadly lacking fullscreen and controller mapping fixes).

@thestr4ng3r

This comment has been minimized.

Copy link
Owner

@thestr4ng3r thestr4ng3r commented Sep 22, 2019

Please run both versions with htop in parallel and check whether you notice any major difference regarding what thread uses how much resources:
Bildschirmfoto vom 2019-09-22 19-28-44
Also please post a log from each version.

@fpiesche

This comment has been minimized.

Copy link

@fpiesche fpiesche commented Sep 28, 2019

I'm running into this as well, on Solus OS 4.0 on a late-2015 Macbook Air (i5 5250U, 8GB RAM, integrated Intel GPU). Using a DS4 connected to the PS4 (logged into Chiaki via an alternate account).

On 1.0.2, 720p60 is perfect, on 1.0.3 even 540p30 gives me at best about 10fps on display (but audio is 100% fine, no stutter or crackling). I'll take a htop snapshot of both versions in a later when I have some time to mess around with the whole thing some more

@fpiesche

This comment has been minimized.

Copy link

@fpiesche fpiesche commented Sep 29, 2019

Here's 1.0.3:
chiaki_session_1.0.3.log
image

@fpiesche

This comment has been minimized.

Copy link

@fpiesche fpiesche commented Sep 29, 2019

Here's 1.0.2:
chiaki_session_1.0.2.log
image

@fpiesche

This comment has been minimized.

Copy link

@fpiesche fpiesche commented Sep 29, 2019

Resource use seems fairly even between the two, and I'm not seeing anything notably different between the logs either...

@thestr4ng3r

This comment has been minimized.

Copy link
Owner

@thestr4ng3r thestr4ng3r commented Sep 29, 2019

Yeah both look reasonable. I will investigate further.

@fpiesche

This comment has been minimized.

Copy link

@fpiesche fpiesche commented Sep 29, 2019

If you'd like me to run with verbose logging or dig around any other system stats, give me a shout and I'll be happy to help :)

@cassidyjames

This comment has been minimized.

Copy link

@cassidyjames cassidyjames commented Sep 29, 2019

I’m also experiencing this on elementary OS 5.0 Juno. For me, both the PS4 and computer are on Wi-Fi. 1.0.2 works very well, with 720p 60fps working great. With 1.0.3 even 360p 30fps is a laggy, unusable affair (like 1fps). The difference is staggering. Happily using 1.0.2 for now. :)

@thestr4ng3r

This comment has been minimized.

Copy link
Owner

@thestr4ng3r thestr4ng3r commented Sep 29, 2019

1.0.3 also had some changes in the build process of the AppImage. You could also try to build from source and compare. That might help us narrow down the issue.

@fpiesche

This comment has been minimized.

Copy link

@fpiesche fpiesche commented Sep 29, 2019

Building from source does indeed work fine!

@alx242

This comment has been minimized.

Copy link

@alx242 alx242 commented Sep 30, 2019

Anyone want to build a new Appimage that doesn't have the weird fps drop?

@thestr4ng3r

This comment has been minimized.

Copy link
Owner

@thestr4ng3r thestr4ng3r commented Oct 1, 2019

@fpiesche @cassidyjames @csfalcione Please post the output of

cat "/proc/`pidof AppRun.wrapped`/maps"

for both versions while the stream is running.

@fpiesche

This comment has been minimized.

Copy link

@fpiesche fpiesche commented Oct 1, 2019

I don't actually have an AppRun.wrapped for the 1.0.2 AppImage, but I've run the above for both of the processes that spawns for me. Here's the results for 1.0.2 and 1.0.3 AppImages and 1.0.3 compiled from source:
chiaki-1.0.2.txt
chiaki-1.0.3-appimage.txt
chiaki-1.0.3-source.txt

@thestr4ng3r

This comment has been minimized.

Copy link
Owner

@thestr4ng3r thestr4ng3r commented Oct 1, 2019

Thanks!

@thestr4ng3r

This comment has been minimized.

Copy link
Owner

@thestr4ng3r thestr4ng3r commented Oct 11, 2019

While I still cannot reproduce this, a lot has changed again in the build process, so I would like to ask you to test these AppImages:
https://transfer.sh/AnXXI/Chiaki-2378db19c6b7a56b105cb2e75da6e16cf2004eec-Linux-x86_64.AppImage (built from xenial)
https://transfer.sh/2xJ52/Chiaki-2378db19c6b7a56b105cb2e75da6e16cf2004eec-Linux-x86_64.AppImage (built from bionic)

@fpiesche

This comment has been minimized.

Copy link

@fpiesche fpiesche commented Oct 15, 2019

The Xenial AppImage still shows the performance issues for me, but the Bionic one works fine!

@alx242

This comment has been minimized.

Copy link

@alx242 alx242 commented Oct 17, 2019

Yeah the Bionic version works for me as well. The current v1.0.4 release has same problems as v1.0.3 had however, guess it wasn't build on Bionic.

@kiwidoggie

This comment has been minimized.

Copy link

@kiwidoggie kiwidoggie commented Nov 17, 2019

Are there new builds available for bionic? (Link is dead) I am also getting around 5FPS in the app, yet alone being able to connect (typing is extremely slow and unresponsive)

AppVersion: 1.0.4
Ubuntu 18.04 LTS (fully up to date)
AMD Threadripper 1950x
AMD RX560
128GB RAM

@alx242

This comment has been minimized.

Copy link

@alx242 alx242 commented Nov 17, 2019

Are there new builds available for bionic? (Link is dead) I am also getting around 5FPS in the app, yet alone being able to connect (typing is extremely slow and unresponsive)

AppVersion: 1.0.4
Ubuntu 18.04 LTS (fully up to date)
AMD Threadripper 1950x
AMD RX560
128GB RAM

I’ve actually haven’t had any problems with the new builds and my bionic machine... not sure why but I works great nowadays :)

@alx242

This comment has been minimized.

Copy link

@alx242 alx242 commented Nov 23, 2019

Realised this was still a issue when I switched to a older kernel, 5.0 instead of 5.3. It worked by running Bionic build of the appImage but it looks like that the upload of those images has stopped working for a while:

$ if [ ! -z "$DEPLOY_FILE" ]; then curl -m 30 --upload-file "$DEPLOY_FILE" "https://transfer.sh/$DEPLOY_FILE"; echo; fi
curl: (28) Operation timed out after 30000 milliseconds with 0 bytes received

Can be seen here: https://travis-ci.com/thestr4ng3r/chiaki/jobs/258696816

Perhaps these builds could be shipped to github together with the other builds....or?

@seuffert

This comment has been minimized.

Copy link

@seuffert seuffert commented Nov 23, 2019

ran into the same problem here. ubuntu 19.04, Kernel 5.3/5.4rc8 :( (Thinkpad T580) couldn't find a recent bionic appimage build to try

Edit:
self compiled current git version runs with high FPS (but some audio distortion)

@thestr4ng3r

This comment has been minimized.

Copy link
Owner

@thestr4ng3r thestr4ng3r commented Nov 25, 2019

Here is a more recent build: https://transfer.sh/51O9j/Chiaki-e3ea1e40b2d805d8dab5e3959ace5f9de304f873-Linux-x86_64.AppImage
I prefer not to ship it on GitHub releases since it's just a workaround. AppImages should generally be built on the lowest supported env.

@elvinasp

This comment has been minimized.

Copy link

@elvinasp elvinasp commented Nov 27, 2019

Here is a more recent build: https://transfer.sh/51O9j/Chiaki-e3ea1e40b2d805d8dab5e3959ace5f9de304f873-Linux-x86_64.AppImage

Issue #10 is shown as closed. However with the build above, when I tried to connect after PS4 powerdown, I saw exactly the same behavior. I was not able to connect to PS4 until I disconnected PS4 controler from PC, pushed my PIN code and then reconnected controller via USB to PC. Is this some earlier branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.