Closed samm81 closed 10 years ago
Hm...I'm not sure we have many alternatives. Other than displaying text, the only other option I can think of is rendering on a canvas.
Maybe we can try innerText or textContent instead? http://blog.stevenlevithan.com/archives/faster-than-innerhtml has a suggestion for speeding things up too.
Another thing we can try is making the arena a
tag or
Any progress on this?
I've been trying I really have I spent hours last night debugging a compiler issue I found some thing saying that changing the css doesn't cause a DOM recalculation, so I'm trying to use font awesome in order to test if having a class specify the content will speed it up I'm working on it!
So I actually misread that article It was actually saying that changing the class is one of the things the * does * cause a reflow Which can take 1-6 seconds So I just did like hours of work I finally got it working, and it was super slow, then I reread the article and headdesked Oh well On a different note, it's actually really fast now I think the issue was just the server basically When I changed the emit timing from .05 to .025 it worked very, very well If the server can actually handle that, then I think this issue is closed.. But I don't know - I can't push to the heroku server I'm gonna make a quick commit to master bringing it up to 60fps, then if you could push that to heroku that would be nice
Pushed to Heroku
So I mentioned this earlier, but it runs pretty slowly for me. Part of this is probably because I'm inside of a VM, but then it won't run smoothly on slower computers. It's just text, for crying out loud. I tried to do it the spans way, because I figured that would speed it up, but it didn't. I did some research and I found this: http://andrew.hedges.name/experiments/innerhtml/
This is terrible, because it suggests the cost of setting innerHTML is 60 ms. That's about two frames, which would explain the lag. I think our whole approach might be flawed.