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

Bug: Performance on Open Pandora is 'laggy' #17

Closed
seclorum opened this issue Mar 7, 2012 · 1 comment
Closed

Bug: Performance on Open Pandora is 'laggy' #17

seclorum opened this issue Mar 7, 2012 · 1 comment

Comments

@seclorum
Copy link

seclorum commented Mar 7, 2012

For some reason, LOAD81 doesn't perform very well on the Open Pandora console - its useable, but seems to be very laggy. Normally such an SDL program on OpenPandora/Angstrom performs very, very well, but with LOAD81 there appears to be some performance issue in the inner loop of the app which results in lag. It is very noticeable with the "text.lua" demo, where the text lags behind the mouse cursors as it moves, by a few milliseconds.

It may be related to a build issue (I have built LOAD81 using the CDEV tools, which is an onboard toolchain which runs on the Pandora itself, -i.e. not cross-compiling, but native compiling on the Pandora hardware itself), or it could have something to do with the overall architecture of LOAD81 itself - is the Lua VM somehow being polled too often, or some other unnecessary code-branch being taken during execution of the Lua script, perhaps?

rlane added a commit to rlane/load81 that referenced this issue Mar 8, 2012
This dramatically reduces the input lag reported in issue antirez#17.
@rlane
Copy link

rlane commented Mar 8, 2012

This issue isn't unique to Open Pandora - I see it on Native Client and even in Linux on my laptop. I sent pull request #24 with a fix.

antirez added a commit that referenced this issue Mar 8, 2012
fast key or mouse UP/DOWN events. This fixes Issue #17.
@antirez antirez closed this as completed Mar 9, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants