Hi All
I really like using Chrome on my S3 and I was bitterly disappointed with the performance I was getting when using it on my TF300T. In my quest to get this thing working as a viable alternative I turned my head towards the shocking internal SD IO performance and the browser2ram hack for the stock browser. I originally planned to fork browser2ram to create "chrome2ram" but instead decided on using DirectoryBind to put Chrome's cache on the ExternalSD card.
** Note: this method does require root **
To prove that this would actually give me a performance increase I used the DirectoryBind trick on Quadrant first and compared the I/O score before and after. Even with my lowly Class2 the figures spoke for themselves - 976 before and 2805 after... wow! Wish I had a faster SD card to hand to retest this with. The config for DirectoryBind was:
So I've now applied this to Chrome and it definitely seems like things have improved - I can't say I've seen an ANR message since I started using this last night. If anyone wants to give this a try and see if they can notice any difference that would be appreciated
. DirectoryBind config for Chrome:
I don't want to bore you with the step-by-step details of setting up DirectoryBind etc. but if there is the demand then I'll put a quick guide together - just make sure you change the settings to bind on boot.
Thanks for reading!
I really like using Chrome on my S3 and I was bitterly disappointed with the performance I was getting when using it on my TF300T. In my quest to get this thing working as a viable alternative I turned my head towards the shocking internal SD IO performance and the browser2ram hack for the stock browser. I originally planned to fork browser2ram to create "chrome2ram" but instead decided on using DirectoryBind to put Chrome's cache on the ExternalSD card.
** Note: this method does require root **
To prove that this would actually give me a performance increase I used the DirectoryBind trick on Quadrant first and compared the I/O score before and after. Even with my lowly Class2 the figures spoke for themselves - 976 before and 2805 after... wow! Wish I had a faster SD card to hand to retest this with. The config for DirectoryBind was:
S: /Removable/MicroSD/QuadrantTemp/ (need to create this folder)
T: /data/data/com.aurorasoftworks.quadrant.ui.standard/
T: /data/data/com.aurorasoftworks.quadrant.ui.standard/
So I've now applied this to Chrome and it definitely seems like things have improved - I can't say I've seen an ANR message since I started using this last night. If anyone wants to give this a try and see if they can notice any difference that would be appreciated
S: /Removeable/MicroSD/ChromeCache/ (need to create this folder)
T: /data/data/com.android.chrome/cache/Cache/
T: /data/data/com.android.chrome/cache/Cache/
I don't want to bore you with the step-by-step details of setting up DirectoryBind etc. but if there is the demand then I'll put a quick guide together - just make sure you change the settings to bind on boot.
Thanks for reading!