I was thinking of possibly changing cache, system and data partitions to F2FS.
In terms of performance and security, is it actually worth the hassle of only getting a few ROMs that support it?
_ASSASSIN_ said:
I was thinking of possibly changing cache, system and data partitions to F2FS.
In terms of performance and security, is it actually worth the hassle of only getting a few ROMs that support it?
Click to expand...
Click to collapse
Check some threads, there was a discussion about it
I think HERE and HERE
As far as I can remember the gains were visible in benchmarks, but even the experienced devs failed to see significant improvement in real life usage.
I'm using f2fs on temasek rom.
I did notice a slight real life improvement. Though cannot say that it's a must have.
For example "optimizing apps" after a wipe of cache runs twice as fast. And for a flashaholic it's fun to see.
Related
hey guys. was wondering what is the best cache size for the internal memory? I believe by default it is 2048. I get an option ranging up to 6144. should I go for the max? Is the improvement significant? and does it affect battery life? Thanks guys!
azreen91 said:
hey guys. was wondering what is the best cache size for the internal memory? I believe by default it is 2048. I get an option ranging up to 6144. should I go for the max? Is the improvement significant? and does it affect battery life? Thanks guys!
Click to expand...
Click to collapse
Why don't you test it yourself amd tell us?
https://play.google.com/store/apps/details?id=ales.veluscek.sdtools
You can go higher than specified on the stock setup of 2048, and you might get an increase in certain scenarios, but keep in mind that the read ahead is mostly effective in its nature of fetching that chunk of data for a purpose. Not just to get filled up with wasted data you aint gonna need anyway. It can be fine for speeding up eg. Browsing your pictures with Quickpic, but you probably waste a good chunk of cachespace that could be more usefull for data you actually need in a fast sequencial read scenario.. Most of what advices for the readahead Ive read from the old dogs on xda points at a 512kb set, as a balance between effectiveness and wasted cache, atleast on phones, but it could be a tad different on our tabs as they are already at 2048 probably for a reason. So digg in and let us know how you fare
Omnius
Sent from my A510 using xda app-developers app
I was wondering why people keep on asking to try it by myself, It doesn't hurt to ask before trying right?
and yes I have tried increasing it and I don't see any improvement with the read speed(since write speed is not going to be affected as been told in a forum topic)
I believe omnius001 was right, it could have been set to 2048 for a reason or two, so increasing won't do better, let's just stick to 2048 then thanks for replying anyway!
azreen91 said:
I was wondering why people keep on asking to try it by myself, It doesn't hurt to ask before trying right?
Click to expand...
Click to collapse
Well, as we say, no guts-no glory It really doesn't hurt anything.
The problem is that all stock Acer tabs suffer from a very poor IO, mostly when it comes to DB writes and other IO functions. Running a simple Quadrant benchmark at standard setting will affirm this. Just look at the IO results. The poorest of any device out there, and poorest by a lot!
Not sure whether this is because of the "noop" scheduler Acer insists on using. Generally, this is an ok scheduler, however BFQ handles things better in my opinion.
Tweaks to improve IO performance have been around for awhile. Generally, as in the Iconia Tab series, it involves some changes in ramdisk, and not the kernel itself. Unless Devs add the BFQ scheduler, which requires a kernel rebuild.
I have a modified kernel (701), unfortunately, never got a chance to test it, before the CWM recovery borked. If I compare to the 501, it should increase IO performance by 400%, more inline with other devices.
Why Acer in 2 years, hasn't improved IO performance when they easily can, well, it escapes logic.
MD
Seems everybody is trying out F2FS, but I've been pretty happy with the existing setup on my TF300T. I know it's "flash-friendly" but what exactly does that *mean*? Longer life on my flash memory? Better speed and performance? And if so, are we talking incremental improvement or really noticeable changes? Aside from curiosity, is there really a reason to change it?
Current setup is CM11 with GEASS kernel (not F2FS)
Thanks!
TM
tmoulder said:
Seems everybody is trying out F2FS, but I've been pretty happy with the existing setup on my TF300T. I know it's "flash-friendly" but what exactly does that *mean*? Longer life on my flash memory? Better speed and performance? And if so, are we talking incremental improvement or really noticeable changes? Aside from curiosity, is there really a reason to change it?
Current setup is CM11 with GEASS kernel (not F2FS)
Thanks!
TM
Click to expand...
Click to collapse
The lowest Quadrant scores on my TF300 were always the memory and i/o scores. I just upgraded my CROMBi-kk (_that kernel) to F2FS and it bumped those scores up from "disasterous" to something like 5 times what they were before. I don't have my tablet with me to check, but I have definitely noticed an improvement since I made the change.
ddd3astra said:
The lowest Quadrant scores on my TF300 were always the memory and i/o scores. I just upgraded my CROMBi-kk (_that kernel) to F2FS and it bumped those scores up from "disasterous" to something like 5 times what they were before. I don't have my tablet with me to check, but I have definitely noticed an improvement since I made the change.
Click to expand...
Click to collapse
:good: When I moved to F2FS, I saw a pretty significant improvement as well.
although this thread doesn't belong here, in Android Development, and should be in General or Q&A, it is a VERY good question...
For this device (T300T) I have noticed a GREAT improvement in performance. I read in the Nexus 5 (hammerhead) forums that F2FS mainly improved write speed over read.
I read a good deal about Flash Friendly File System, and learned only that much without trying it. I am not always in the mood for doing more research than necessary. . . I learned how to convert to it, how to restore back; the errors that occor and how to correct them; the potential dangers; and then i re read the instructions and the forums regarding them.
On my Nexus 5 I'm amazed at the backup speed in TWRP and have found great performance enhancement, though its a Nexus 5, so its quite difficult to "feel" the difference unless you mess around with your device a ton (kernels roms OC etc) and THEN switch to it.
with this device, I have noticed a near-night and day difference since switching over. All I did was back up my data/media to my microSD and format using GEASS's provided recovery and flashed CM 11 back on and flashed Hardslog's grimlock kernel and then gapps. I used nandroid manager to restore my apps from a nand i made b4hand and copy and pasted whatever files I wanted on my tablet (which were few) internal memory.
Voila! my tab is sexy again.
Not sure about the whole F2FS All thing (reformatting all partitions to f2fs) its mentioned more in the hammerhead forums, and have read mixed reviews.
but its definitely worth a shot if youre not afraid of doing a little bit of reading and a little bit of dirty work, as it is quite beneficial on this tab
the end...for now
Greetings fellow Infinity owners! I am a new owner of this amazing tablet ever since I bought it from my friend for $250 this evening. I don't know if it's a good deal but as for now I'm pretty happy with it, and looking forward to be even more happier when I install custom ROM in it.
I have been a loyal user of CyanogenMod ROMs, but considering this device is unique (mainly because of its dock), I would like to know whether CM ROMs are compatible to use with the dock. Or maybe there's even better ROM out there for this tablet? As for now I don't have the dock but I'm thinking of buying it next month.
Please share your thoughts and suggestions (if any)!
The only rom fully compatible with the dock is CROMi-X 5.4 since it's based on the Asus stock rom.
The CM based roms like CM11 and CROMBi-KK work with most dock functions, but there are bugs, e.g.
If you use the Volume buttons on the dock, the tablet's power button stops working.
If you close the lid of the tablet/dock combo the screen does not turn off as it would with CROMi-X.
Development on CROmi-X is stuck since Asus did not release new firmware after JB 4.2.1.
CM and CROMbi-KK are at JB 4.4.3
berndblb said:
The only rom fully compatible with the dock is CROMi-X 5.4 since it's based on the Asus stock rom.
The CM based roms like CM11 and CROMBi-KK work with most dock functions, but there are bugs, e.g.
If you use the Volume buttons on the dock, the tablet's power button stops working.
If you close the lid of the tablet/dock combo the screen does not turn off as it would with CROMi-X.
Development on CROmi-X is stuck since Asus did not release new firmware after JB 4.2.1.
CM and CROMbi-KK are at JB 4.4.3
Click to expand...
Click to collapse
If you had to pick one of those 3, what would be the most stable in terms of performance?
I flashed mine to the latest snapshot version of CM11 last night. Though it's newer, it's not necessarily faster than the stock Asus 4.2.1 firmware, I can say the performance has been very bad. So I went on and try the nightly version, which did not change anything in the big picture: it's still sluggish.
I haven't tried CROMi or CROMbi, but assuming CROMbi is based on CM11, is it safe to say that it's just as sluggish as CM11 itself?
Anggrian said:
If you had to pick one of those 3, what would be the most stable in terms of performance?
Click to expand...
Click to collapse
Usually there is a trade-off between stable and fast.
Anggrian said:
I flashed mine to the latest snapshot version of CM11 last night. Though it's newer, it's not necessarily faster than the stock Asus 4.2.1 firmware, I can say the performance has been very bad. So I went on and try the nightly version, which did not change anything in the big picture: it's still sluggish.
Click to expand...
Click to collapse
Details? How do you measure performance?
_that said:
Usually there is a trade-off between stable and fast.
Click to expand...
Click to collapse
With that consideration, which is the fastest and most pleasant to use?
_that said:
Details? How do you measure performance?
Click to expand...
Click to collapse
I measure performance by how smooth the OS navigation is.
Which in this case, is very poor. First off, swiping pages in Google Now Launcher is far from smooth, especially swiping the most left to Google Now interface, sometimes it freezes on the way. Capacitive buttons (back, home, recent apps) take 1-3 seconds to react, which is also the same amount of delay needed to open Settings. Lastly, even pulling notification bar isn't always smooth.
If you're interested, I could shoot a quick video to show how painful the navigation is. In a way I also wonder if this level of performance is normal in TF700T.
Anyway, as been told by other threads, I wiped dalvik cache and cache while in CWM recovery, issue remains.
The TF700T has never been the fastest or smoothest of its generation, but it should not be painful to use.
Try installing CROM(b)i - it has a lot of performance tweaks.
Anggrian said:
With that consideration, which is the fastest and most pleasant to use?
I measure performance by how smooth the OS navigation is.
Which in this case, is very poor. First off, swiping pages in Google Now Launcher is far from smooth, especially swiping the most left to Google Now interface, sometimes it freezes on the way. Capacitive buttons (back, home, recent apps) take 1-3 seconds to react, which is also the same amount of delay needed to open Settings. Lastly, even pulling notification bar isn't always smooth.
If you're interested, I could shoot a quick video to show how painful the navigation is. In a way I also wonder if this level of performance is normal in TF700T.
Anyway, as been told by other threads, I wiped dalvik cache and cache while in CWM recovery, issue remains.
Click to expand...
Click to collapse
Whenever you switch roms, no matter if they share the same base, wiping of cache and dalvik is not enough. You have to clean install, meaning at least a factory wipe in recovery, if you really want to experience the potential (or lack of thereof) of that rom.
I do not experience the lag you describe on the latest CROMBi-KK install and I did not on CROMi-X either. But then - I don't even install Google Now and other "social" cr*** - so YMMV.
CROMBi-KK is the fastest and smoothest rom I have run on this tablet, but it does have the dock bugs I mentioned earlier.
_that is right - there's always a trade off between reliability and speed.
Try the CROMi roms (either X or KK) and install them with fsync off and I bet most of your complaints will be gone. The biggest performance boost for this tablet (with it's build-in slow memory) is to run it with fsync off or data2sd on a fast microSD. If you want full dock compatability it's CROMi-X, if you want KitKat goodness it's CROMBi-KK.
Have fun testing!
berndblb said:
Whenever you switch roms, no matter if they share the same base, wiping of cache and dalvik is not enough. You have to clean install, meaning at least a factory wipe in recovery, if you really want to experience the potential (or lack of thereof) of that rom.
I do not experience the lag you describe on the latest CROMBi-KK install and I did not on CROMi-X either. But then - I don't even install Google Now and other "social" cr*** - so YMMV.
CROMBi-KK is the fastest and smoothest rom I have run on this tablet, but it does have the dock bugs I mentioned earlier.
_that is right - there's always a trade off between reliability and speed.
Try the CROMi roms (either X or KK) and install them with fsync off and I bet most of your complaints will be gone. The biggest performance boost for this tablet (with it's build-in slow memory) is to run it with fsync off or data2sd on a fast microSD. If you want full dock compatability it's CROMi-X, if you want KitKat goodness it's CROMBi-KK.
Have fun testing!
Click to expand...
Click to collapse
Informative! Will try CROMi-X tonight!
Oh 1 more thing, I am currently in CWM recovery, do I need to switch to TWRP recovery to install CROMi or CWM does just well?
Anggrian said:
Informative! Will try CROMi-X tonight!
Oh 1 more thing, I am currently in CWM recovery, do I need to switch to TWRP recovery to install CROMi or CWM does just well?
Click to expand...
Click to collapse
As long as it is CWM 6.0.4.6. or later (and you don't want to try the f2fs file system on /data) you're ok.
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------[/SIZE
Edit: I do run the rom with internal data formatted to f2fs. It does make a difference.... For f2fs you need TWRP 2.7.1.1
berndblb said:
As long as it is CWM 6.0.4.6. or later (and you don't want to try the f2fs file system on /data) you're ok.
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------[/SIZE
Edit: I do run the rom with internal data formatted to f2fs. It does make a difference.... For f2fs you need TWRP 2.7.1.1
Click to expand...
Click to collapse
I had no idea what f2fs is so I went on and googled it. According to this thread: http://forum.xda-developers.com/showthread.php?t=2681775, it can cause data loss on the exchange of performance gain.
Based on your experience on f2fs, what do you have to say about that?
Sent from my Nexus 5 using XDA Free mobile app
Anggrian said:
I had no idea what f2fs is so I went on and googled it. According to this thread: http://forum.xda-developers.com/showthread.php?t=2681775, it can cause data loss on the exchange of performance gain.
Based on your experience on f2fs, what do you have to say about that?
Click to expand...
Click to collapse
I can confirm the performance gain (subjectively - hard to really measure it except with benchmarks. And I don't believe in those...) and I haven't had any data loss - yet
I treat any data on a mobile device as being just one step away from going down the drain - it happens often enough. If you want to try anything experimental, a solid backup/sync routine is a must in my book.
f2fs and also fsync off both fall into that category. I have run my tablets with fsync off for more than a year without any problem, but I have less experience with f2fs.
You just gotta be careful. I wouldn't try, let's say, ART runtime AND flash the new Asus apps package on CROMBi-KK with /data formatted to f2fs - risks grow exponentially if you combine them.....
Anggrian said:
Greetings fellow Infinity owners! I am a new owner of this amazing tablet ever since I bought it from my friend for $250 this evening. I don't know if it's a good deal but as for now I'm pretty happy with it, and looking forward to be even more happier when I install custom ROM in it.
I have been a loyal user of CyanogenMod ROMs, but considering this device is unique (mainly because of its dock), I would like to know whether CM ROMs are compatible to use with the dock. Or maybe there's even better ROM out there for this tablet? As for now I don't have the dock but I'm thinking of buying it next month.
Please share your thoughts and suggestions (if any)!
Click to expand...
Click to collapse
Try the Techfusion+ Rom and install Asus keyboard and Keyboard Manager manually. It is 4.4.3, very fast and doesnt get laggy over time. Best thing us Battery life, which is far better than on the other ROMs
Hello i am a bit confused if starting to use F2FS system or not.
Can an User give me hes opinion?
and does it work with MultiROM?
F2FS brings better write speeds, but worse read speeds. Also, F2FS is still really new and could bring data loss. And finally, if you decide that you've had enough of f2fs, you have to wipe and start over by converting the filesystem back into ext4
I personally would stick with ext4. The negligible speed difference is not worth the problems that come with f2fs
It's been a while since I managed this stuff myself so I'm foggy on how to troubleshoot, but something along the lines of I don't have an /etc/fstab or it's empty so swapon is failing.
previously used FauxClock to manage this, unsure why it's not working like it used to.
thor1k said:
It's been a while since I managed this stuff myself so I'm foggy on how to troubleshoot, but something along the lines of I don't have an /etc/fstab or it's empty so swapon is failing.
previously used FauxClock to manage this, unsure why it's not working like it used to.
Click to expand...
Click to collapse
well, to answer the question in the title.. because its pointless. zram/zswap is good for our old devices(like g1 or old school droid), with low ram. as thats what you are using the zram/zswap for, to increase ram. the nexus 5 has 2gb ram, i bet you will never run low on ram with a nexus 5. and if you think its a benefit to the nexus 5, then you are living in a placebo.
what happened to yours, i have no idea.
simms22 said:
well, to answer the question in the title.. because its pointless. zram/zswap is good for our old devices(like g1 or old school droid), with low ram. as thats what you are using the zram/zswap for, to increase ram. the nexus 5 has 2gb ram, i bet you will never run low on ram with a nexus 5. and if you think its a benefit to the nexus 5, then you are living in a placebo.
what happened to yours, i have no idea.
Click to expand...
Click to collapse
can you help me get it back?
I feel like a FauxClock update broke it.
What it was actually doing was a bit more complicated, virtualizing the diskspace (compressed, too) as a buffer layer on top of the flash. This improved random read and especially random write performance which helped with multitasking a LOT as resume from suspend in the app lifecycle was resuming from RAM, not from flash. This meant less hitching/FPS drops when bringing up android recents, as well as during animation/draws when switching to the other app
This is the only reason I want it. Simply as swap space, yes not necessary
thor1k said:
can you help me get it back?
I feel like a FauxClock update broke it.
What it was actually doing was a bit more complicated, virtualizing the diskspace (compressed, too) as a buffer layer on top of the flash. This improved random read and especially random write performance which helped with multitasking a LOT as resume from suspend in the app lifecycle was resuming from RAM, not from flash. This meant less hitching/FPS drops when bringing up android recents, as well as during animation/draws when switching to the other app
This is the only reason I want it. Simply as swap space, yes not necessary
Click to expand...
Click to collapse
that sounds what disabling fsync would do, help with random read and write. have you tried just disabling fsync? anyways, its your kernel that will have the zram feature, reflash it. if you have flashed/updated your rom, the kernel should be reflashed.
simms22 said:
that sounds what disabling fsync would do, help with random read and write. have you tried just disabling fsync? anyways, its your kernel that will have the zram feature, reflash it. if you have flashed/updated your rom, the kernel should be reflashed.
Click to expand...
Click to collapse
no fsync is totes different
current guess is no init.d script for the zram because restored fauxclock from titanium and enable/disable only modifies the script, relying on the script existing in the first place, and it doesn't because I didn't manually install it myself. Uninstalling and reinstalling fauxclock doesn't work though, it's like certain settings persist somewhere. It's always been a bit goofy like that, and I don't feel like wiping and installing just for the ZRAM at this moment. Currently waiting on someone to post their zram init.d script, or if anyone here sees this and wouldn't mind uploading it, much obliged.
another question: how can I low-level format the phone? IE not just wiping the partition, but actually checking for bad blocks and cutting them out of the flash table. I have another phone that I think needs that, but all the CWM and TWRP recoveries seem to just do wiping not complete formats.
init tasks are somewhere besides /etc/init.d now it looks like
if anyone else needs it, flashing completely stock image straight from google and then rooting got me what I needed. Unsure why the "stock rooted" zips people provided weren't good enough. oh well