Emulationstation CPU usage

meleu

@Hex I'm not sure... Once the branch is merged there's no need to keep it in the list IMHO.

I'm planning to work out my git-fu and try to find a way to get the branches from the open Pull Requests list in the EmulationStation repo and build a list based on that info. It would pretty cool, huh? :-)

It seems that you're more experienced with git, do you know how to do that (get a list of open PRs and their respective repo/branch)?

I've found some documentation here but didn't find enough free time to dive into it. I am planning to use curl to get the needed info...

meleu

do you know how to do that (get a list of open PRs and their respective repo/branch)?

Getting the info in a JSON format:
https://api.github.com/repos/RetroPie/EmulationStation/pulls?status=open

Now I need some time to learn how to use jq:
https://stedolan.github.io/jq/

Looks promising! I'll try to release something next weekend! ;-)

Hex

Json makes it very easy. I was already starting with curl (mobile page)+regex. I will let you know if i finish .

Hex

@meleu How about this

Get page from github

curl https://api.github.com/repos/RetroPie/EmulationStation/pulls?status=open > page

Loop over all PRs

n_pr=$(($(cat page | ./jq-linux64 'keys | length')-1))
for i in `seq 0 "$n_pr"`; do
     cat page | ./jq-linux64 ".[$i] | {name: .user.login, title: .title, branch: .head.ref}"
     # Do individual processing here eg. add each item to list
    echo "Yolo \m/"
done

# Or get all PRs in single operation
cat page | ./jq-linux64 ".[] |  {name: .user.login, title: .title, branch: .head.ref}"

Output

{
  "name": "pjft",
  "title": "Adding support for \"All\", \"Favorites\" and \"Last Played\" systems",
  "branch": "RetroPie-Virtual-Systems-PR"
}
{
  "name": "nschloe",
  "title": "various code fixes",
  "branch": "coverity-retropie"
}
{
  "name": "PronkMedia",
  "title": "Added a new (missing) transition style, 'carousel slide'.",
  "branch": "master"
}
{
  "name": "sokie",
  "title": "Implemented favourites system",
  "branch": "favourites"
}
{
  "name": "seriema",
  "title": "OSX compilation fixes",
  "branch": "osx-compilation-fixes"
}

meleu

@Hex by the way, I have a raspi1 and I'm interested in test your branch. What's its name?

Hex

@meleu Its my master branch. It has all tweaks and works. I was thinking of separating the feature so that a pull request can be optionally submitted. The only downside is Screensaver is not triggered as the Pi waits for user input and stops rendering new frames as there is literally nothing to do. Although it can be manually triggered by pressing "select" in systems menu

cyperghost

@Hex said in Emulationstation CPU usage:

@Sano , @cyperghost would you guys be interested in testing this feature for me? I am interested in submitting this as a feature. It is quite stable for now but not ready for merge. As such testers would be most welcome.

Sure! I can test this on a RPi 2 - would you offer ready compiled binaries?
Is it enough to just exchange the binary from /opt/emulationstation?
Why do you use OMXPlayer as background player? I think mpg123 is less resource hungry and it's simple command structure is excellent in saving memory space.

meleu

@Hex Yeah! That feature was added. Posted about it here: https://retropie.org.uk/forum/post/88716

Now I have to find some time to merge those improvements you made on your version of script...

Cheers!

finh

Anyone experiencing this, using the "power saver modes" option solved the problem for me. The menu option is at start -> other settings -> power saver modes. Enhanced and instant worked well.

I'm using V2.6.3RP, on a Raspberry Pi 3 B. Idle, even with the screensaver set to a black screen, the emulationstation parent process would be at 30% cpu usage or more. On "instant," it ranges between 5% and 10%.

I realize this is an old post, but it's the only thing that came up in my search on this particular issue.

praetorian55

Thanks for that tip finh! I was trying to troubleshoot cpu usage on x86 emulationstation and happened on your post, works perfectly to address cpu usage!