For those concerned with lagging/stalling as in other Galaxy S models

---

Take a look at this: http://www. laptopmag.com/review/cell-phones/samsung-epic-4g.aspx?mode=benchmarks&cids=2214,2290,pa

Go to that page and add the other Galaxy S variants to the comparison charts and check the FileSystem benchmarks. As you will see, The Epic 4G beats the other phones 5+ times over, and even destroys the EVO 4G's score by a little over 4 times. This is great news for those of us concerned about the lower ROM capacity!

They are missing a lot on those benchmarks. I can't find the nexus one at all, and the linpack benchmarks all seem to be testing android 2.1 phones. I think what people are afraid of with this phone is that the JIT compiler works amazingly for Snapdragon processors but not for TI OMAP processors or the Samsung Hummingbird cpu. People are claiming extremely high scores in Linpack with afaik is a cpu benchmark utility. Now All of the Cortex A8 1 ghz processors should have the same performance give or take 5-10% variance. However Snapdragon cpus seem to get 30-50 on linpack with 2.2 on the nexus one and evo 4g, but the droid 2 only gets 13-14, and what few beta or alpha builds of 2,2 have leaked for galaxy s phones they seem to get similar scores. This is what worries people. However I think we need to wait and see why the droid 2 is getting such low scores on 2.2 and see if the official smasung 2.2 build gets similar low scores.

Also that site says that the droid x/2 has the same gpu performance as the epic 4g and on top of that the evo 4g scores less than 10% below them. Last I checked the power vr 530 in the x/2 is half as powerful or less than the 540 in the galaxy s phones and the amd gpu in the snapdragon processors is supposed to be even weaker than the 530. Given this knowledge I have to say those benchmarks are fairly unprofessional.unscientific and useless as they are clearly biased.

There's no denying the inaccuracies in the majority of benchmark tests, but the only one I want you to see is the FileSystem benchmarks. Not the cpu or gpu ones. FileSystem measures how fast the storage/memory on the phone is writable and readable. The Galaxy S phones have an issue where out the box all the apps are stored on an internal class 2 SD card, instead of the faster internal NAND memory causing severe lag and even stalls when transitioning between screens. That has been fixed through a hack though, which requires reformatting the file system and 1.5 GB of internal memory which the Epic doesn't have, making a fix impossible for the time being if indeed there is a lag/stall issue on the Epic 4G.

The benchmark for FileSystem, if accuratee, is a sigh of relief, cause it seems like there will be no lagging or stalling between transitions out the box with the Epic 4G. Let's hope This is the case, otherwise it will be a huge deal breaker. The Vibrant can take up to 10 seconds to get back to the home screen from an app when the home icon is pressed. That would really kill the experience if it's present in the Epic 4G and unable to be fixed due to low ROM.

I don't put much stock in benchmarks, but I believe he was trying to point out just 1 benchmark in particular that shows that the Epic doesn't suffer from the flaw in the Captivate\Vibrant that causes the slowness. It's interesting that the benchmarks didn't include Quadrant... which the Captivate\Vibrant somehow destroy all over phones in without 2.2 post lag fix. I'd be interested to see how the Epic performs out of the box there... but I can wait.

My bad I was just tired and didn't realize it was the filesystem speeds that were being pointed out. Though I still question this sites benchmarks and would love to know what software they used for each one.

Does anyone find it odd that the droid 2 and droid x have different filesystem benchmark speeds? I would have assumed they had the same storage and file system. However the droid 2 on 2.2 is showing speeds considerably slower than the droid x in benchmarks for that. It just makes me wonder if it is 2.1 and 2.2 just being wonky, or do these benchmarks possibly have little to no meaning.

Nice find. This test has to be running from the internal memory since it scores the same as the droid x with 8 gig internal storage. The epic has less then 500 mb of internal storage so the sd card has to come into play after the internal storage is full. The issue with that is the sd card runs 2 to 3 times slower then the internal memory. My class 6 sd card with ext2 partition scores 1000 and my captivates internal storage with ext2 partition scores 2600. This may never be a issue if you only install limited amount of apps to internal storage and music, video, games and pics to sd card. This is the only thing holding me back from the epic right now since I have a lot of games that I want on the internal storage. I will have to test and see if it even makes a real world difference. If it doesnt make a real world difference then the epic will be my new phone for sure if the gps issue is really fixed.

My sources tell me, the quadrant score was 889 on the epic 4g

Originally Posted by noobnl

My sources tell me, the quadrant score was 889 on the epic 4g

Hmm thats weird. That means the ****ty partitioning that causes the lag is not gone. The captivate gets 900+ with no lag fix. It gets over 2500 with ext2 internal partition lag fix applied. It doesn't really matter for the captivate since there is internal storage ext2 lag fix but that wont work on the epic since it does not have enough internal storage. They will have to use the slower sd card lag fix. I really dont think they changed the way samsung partitions the storage just for the epic but we will see soon enough.

or maybe they are adding RFS R/W buffer in their 2.6.32 kernel for FroYo

So this means if there is a "lag" or whatever, for those unfamilar with all the tech stuff..I'll be stuck with a broken phone? That sucks..I'm really psyched but I don't want to be stuck with the epic if either the vibrant or captivate would be better because they have enough memory to fix the lag issue..or would just simply switching roms fix it?