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 Issues With Large Queues #42

Open
hartmantis opened this issue Aug 3, 2011 · 1 comment
Open

Performance Issues With Large Queues #42

hartmantis opened this issue Aug 3, 2011 · 1 comment

Comments

@hartmantis
Copy link

Given TTfm's occasional bugginess, I had always assumed this was their fault, but it appears to be the Turntable.fm Extended extension that's slowing down the interface.

I have 780 items in my queue. When I enable the Turntable.fm Extended extension, the head-bobbing animations become severely choppy and clicking repeatedly in any area of the interface causes all the animations to seize up for up to several seconds.

This occurs in all of the latest stable, beta, and dev Chrome builds, and I have reproduced it in the latest versions of Mac OS X, Ubuntu, and Windows 7. Doesn't seem to make a difference which features of the extension I have enabled or disabled, as long as the extension itself is turned on. Disabling all other extensions does not help, and there are no errors present in the Javascript console.

When I signed in with a dummy account with no queue and the extension enabled, these issues did not present.

If there's any further info I can provide, I'd be happy to; I just don't know much of anything about how Chrome extensions work or what info might be valuable. Is there anything I might try to enhance performance aside from paring down my queue? Or is this something inherent in how the extension needs to be to work with the TT interface?

Thanks!

@MarkReeder
Copy link
Owner

There are a few things that need to run constantly in order to provide some of the functionality, but there shouldn't be anything involving the queue that needs to run constantly. I'll dig into this soon and see if I can nail down what's causing the slowdown.

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

No branches or pull requests

2 participants