Discourse is slow on Android. Why?
-
Those are amazing numbers for Android.
I am telling you guys when the V8 fixes land it is going to be a dramatic improvement. For everyone on all devices, and not just our stuff but in general for heavy JS code. The best kind of upstream fix that attacks the disease not just the symptoms.
-
So from:
http://what.thedailywtf.com/t/discourse-is-slow-on-android-why/4417/14?u=loopback0
With Chrome as the only app open
To:
1021ms
With enough other apps open that the phone is warm. I'll give it another go later with just Chrome for a fairer comparison, but if this number translates to that big a performance improvement then cool.
-
Yep, this is the GamerGate reply. Believe it or not, it is possible to enjoy something, but still criticize aspects of that thing it in hopes that it might one day improve. Shocking, I know.
Seriously, you're going to compare a small amount of topic derail to the controversial isolating sexualization of the female gender in video games.
"Fuck off"
God, people have lost all kind of sensibility for false sensitivity.
It's bullshit like this that makes it impossible to comes to terms with any real problems.
-
This hasn't exactly improved things though - see @Frostcat's score in @sam's topic, after the changes, on an LG G3 which is a new, top end phone.
Not only that, and I hate to seem like I'm piling on, but the primary effect reducing the batch size seems to have is increased pausing while scrolling, because you have to load data more frequently.
-
Not seeing those results, we need new ones pretty much today
So literally Sunday is too old? No problem, I will check again right now. I'll even reboot the phone first in case I have any games in memory.
-
No screenshot as I haven't figured out how to do it yet, or else I'm just doing it wrong.
3318 at first, then it seemed to settle down at 3404 or so. So that's a nice improvement over the weekend, but it still seems to be pretty darn slow. Again, this is Chrome on an LG G3, right after rebooting the phone.
Then I loaded the URL in the stock browser, It starts off at 3883, goes to 3895, and then 3974. I think that's actually worse, but I'd have to find my original post.
-
No screenshot as I haven't figured out how to do it yet, or else I'm just doing it wrong.
hold power and volume down for a couple of seconds and it'll snap a screen shot.
at least according to the AOSP docs. no guarantees if you have a carrier overlay.
-
I know about that. I was unable to make it work. The G3 places the buttons oddly, so it's awkward to press them both at the same time. @chubertdev or someone has the same phone, maybe he can chime in on any trouble he had.
There's supposed to be another LG-specific way but I haven't been able to get that to work yet either. I'll admit I haven't spent a lot of time on either method.
-
aaah... samsung. in that case i'm afraid this clause probably applies:
@accalia said:no guarantees if you have a carrier overlay.
-
aaah... samsung.
G3 = LG
Samsung since the GS3/S3 is easy enough - edge of your hand on the left side of the screen, swipe across to the right.
-
G3 = LG
-shrug- so i got the company wrong.... if it's not AOSP then it's got a carrier overlay on it. it's only a matter of how annoying the overlay is.
-
Samsung since the GS3/S3 is easy enough - edge of your hand on the left side of the screen, swipe across to the right.
Yup, I used to do that on my Note 2.
It turns out on the G3 you have to hold the power/volume down, not just press it. Also, since the power button is in between the volume ones in the middle of the back, it takes a bit of practice.
-
It turns out on the G3 you have to hold the power/volume down, not just press it.
That's how it is on stock. You don't have to hold it for long, but just tapping the combo won't do it.
It's about a second.
-
That's how it is on stock. You don't have to hold it for long, but just tapping the combo won't do it.
It's about a second.
That's what I found out this morning. But look at the unusual button layout. the lighter colored circle is power, the darker oval around it is the volume up/down. You need to experiment a couple of times to hit them both together right.
http://techie-buzz.com/wp-content/uploads/2014/09/lg_g3_back.jpg
-
Also, I got the blue one instead of this color.
-
Visually it looks like you'd just have to push the bottom 2/3 (i.e. everything but volume up) but I don't know what the physical buttons are like on that.
Another thing though, I thought your numbers looked pretty high especially for a recent device, so I tried that test on my Nexus 5 just now and got 2267. How is it that my phone, equivalent to a generation behind yours, gets better performance? Is the LG stuff really that heavy weight?
-
if it's not AOSP then it's got a carrier overlay on it.
As the carrier is the MNO/MVNO then if it's not AOSP then it's got a manufacturer overlay on it. Some then, additionally, have a carrier overlay/tweaks added on top of that.
-
E_QUOTA_EXCEEDED returned trying to award pedantry badge. please try again later.
;-)
-
I'm not in it for the badgers. ;)
-
hmm.. carry on then.
-
I know about that. I was unable to make it work. The G3 places the buttons oddly, so it's awkward to press them both at the same time. @chubertdev or someone has the same phone, maybe he can chime in on any trouble he had.
There's supposed to be another LG-specific way but I haven't been able to get that to work yet either. I'll admit I haven't spent a lot of time on either method.
I have a Samsung GS3, and don't even bother to visit this site on it.
-
Visually it looks like you'd just have to push the bottom 2/3 (i.e. everything but volume up) but I don't know what the physical buttons are like on that.
That's correct. Like I said, you gotta learn how the buttons activate, though, if you know what I mean.
-
certainly people are used to OS versions determining this stuff since on iOS (and AFAIK Windows Phone and Blackberry and what ever other fraction of a percent mobile platforms there are) you have to update the OS to get a new browser version. Android is kind of the outlier in this regard
You're forgetting one thing: people often pick one phone OS and stay with it. They get used to the way that OS works and don't expect anything else. Telling an Android user what their requirements are based on how iOS works is stupid.
-
No screenshot as I haven't figured out how to do it yet, or else I'm just doing it wrong.
For your G3, press power and volume down simultaneously. I find it easiest to do with two fingers/both hands.
-
Yeah, I managed to figure it out, but thanks. With a bit of practice, I can do it with one finger. That feels a bit less awkward than trying to reach both buttons with two fingers or two hands.
I was concerned about the button placement, but the power button can be reached fairly naturally when I'm holding the phone in my left hand.
-
It starts off at 3883, goes to 3895, and then 3974. I think that's actually worse, but I'd have to find my original post.
Yeah per the original bug entry one side effect of the Chrome android V8 issues is how it constantly optimizes and deoptimizes the JS as it runs, causing massive perf issues, manifesting as huge standard deviations.You would expect to see lots of variability in runtime as a result. All the Android benches in Ember show this to the point that it is hard to tell if anything is getting faster.. 3 sec with a standard deviation of 1.5 seconds? Is that better than 2.5 sec with a standard deviation of 1.5 seconds?
All of which will hopefully go away when the V8 fixes land in a version of Chrome you can download from the Play Store.
-
BTW, following this:
http://what.thedailywtf.com/t/discourse-is-slow-on-android-why/4417/502?u=loopback0
(Good oneboxing there btw)It was 2321.67ms on Ember 1.8, then as a fairer test has been rerun just now with only Chrome open and it's now 792.7ms.
Huge improvement if this translates into real-world performance.
-
Well we know Android rendering gets exponentially worse as you add more content so rendering half as much for now at least keeps our head above water. @sam also deferred a bunch of stuff that was needlessly rendered at page load time which helps all platforms.
As I said we will attack it on multiple fronts, but there is just no getting around the disease (getting V8 Android fixed) vs. the symptoms.
-
Android 2.3 Gingerbread—Four years later, the OS just won’t die
Android 2.3 Gingerbread—Four years later, the OS just won’t die
Years of support means the OS looks very different today than it did in 2010.
"The OS that originally shipped in 2010 is still clinging on to 9.1 percent of active devices, and in developing markets it still ships on new devices. Android 2.3 has even outlasted newer versions of Android, like 3.0 Honeycomb (0 percent) and 4.0 Ice Cream Sandwich (7.8 percent)."
" The most important app of any smartphone OS is the app store, and Google has made sure to not leave Gingerbread behind—as you can see in the main article picture, the OS gets the very latest version of the Play Store."
-
Samsung since the GS3/S3 is easy enough - edge of your hand on the left side of the screen, swipe across to the right.
Which is kind of annoying, because I am used to doing that to wipe the smudges from the screen. Now when I do it...screen shot every time. I am getting used to it though.
