Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Android Devices > enTourage eDGe

Notices

Reply
 
Thread Tools Search this Thread
Old 02-20-2014, 10:16 PM   #1
helf
Zealot
helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.
 
Posts: 122
Karma: 500250
Join Date: Jun 2011
Device: Entourage Pocket eDGe, Entourage eDGe, Samsung Galaxy Note II
Performance Boost: Enabling Dalvik's JIT compiler and increasing heap size<- Read :)

Hey, I forgot you can't change the titles of a post after the initial posting. So I am posting the bit about the Dalvik VM JIT I just noticed on my PE as well as heap size so more people see it.

Some light reading on Dalvik's JIT compiler.
http://android-developers.blogspot.c...alvik-jit.html

Android 2.2 added a JIT (Just-In-Time) compiler to the Dalvik VM. Dalvik is the interpreter that is the heart of Android and runs all your apps. (It is being superseded by ART in latest Android releases)

I was digging around in my build.prop looking for more stuff to do to my PE to try and get as much performance as I could out of the poor old thing when I noticed the Dalvik execution mode line. I did some googling and read up on Dalvik some and decided to try changing it to the JIT instead of the default failsafe "fast" mode. My Linpack results went from 3.1-3.2 MFLOPS average to 5.1-5.2MFLOPS which is a pretty drastic
increase.

The other thing I changed in my build.prop was the Dalvik heap size.I doubled the default heap size to 256MB from 128MB that is the default. The Dalvik heap size adjusts how much memory a Dalvik VM instance can use. The more memory a single app can use, the less often Dalvik has to run through its garbage collection routines. This takes a load off the CPU and may be one reason my PE has seemed so much snappier. This may just be placebo, though. It shouldn't cause any harm and the PE has 512MB of RAM to play with so... worth doing, imo.

Code:
dalvik.vm.heapsize=256M
dalvik.vm.execution-mode=init:jit
I have had my PE running with a 256MB heap for 2 years with no issues and a few days with the JIT on and no problems. I made the same changes to my friends PE today and he hasn't had any problems, either.
helf is offline   Reply With Quote
Old 03-08-2014, 08:04 PM   #2
solarbanjo
Member
solarbanjo will become famous soon enoughsolarbanjo will become famous soon enoughsolarbanjo will become famous soon enoughsolarbanjo will become famous soon enoughsolarbanjo will become famous soon enoughsolarbanjo will become famous soon enough
 
Posts: 23
Karma: 582
Join Date: Jul 2011
Device: Entourage Pocket Edge
And this is exactly why I keep following this forum. Great tip, helf! I just keep finding reasons to love my little Edge...
solarbanjo is offline   Reply With Quote
 
Enthusiast
Old 03-18-2014, 12:29 AM   #3
helf
Zealot
helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.helf ought to be getting tired of karma fortunes by now.
 
Posts: 122
Karma: 500250
Join Date: Jun 2011
Device: Entourage Pocket eDGe, Entourage eDGe, Samsung Galaxy Note II
np! I'm glad people are still checking in. Post your experiences with the VM change, if you want. I'm curious to see how other people fair with it.
helf is offline   Reply With Quote
Old 04-09-2014, 09:45 AM   #4
Gerrye
Zealot
Gerrye began at the beginning.
 
Gerrye's Avatar
 
Posts: 126
Karma: 10
Join Date: Mar 2011
Location: Leblon, Rio de Janeiro, Brazil
Device: 1 EE 3 PEs 2 Blk,1 Red(1 for parts)& Kindle Paperwhite, Notes 2 & 3
Cool Adding some how to the what....

Quote:
Originally Posted by helf View Post
Hey, I forgot you can't change the titles of a post after the initial posting. So I am posting the bit about the Dalvik VM JIT I just noticed on my PE as well as heap size so more people see it.

Some light reading on Dalvik's JIT compiler.
http://android-developers.blogspot.c...alvik-jit.html

Android 2.2 added a JIT (Just-In-Time) compiler to the Dalvik VM. Dalvik is the interpreter that is the heart of Android and runs all your apps. (It is being superseded by ART in latest Android releases)

I was digging around in my build.prop looking for more stuff to do to my PE to try and get as much performance as I could out of the poor old thing when I noticed the Dalvik execution mode line. I did some googling and read up on Dalvik some and decided to try changing it to the JIT instead of the default failsafe "fast" mode. My Linpack results went from 3.1-3.2 MFLOPS average to 5.1-5.2MFLOPS which is a pretty drastic
increase.

The other thing I changed in my build.prop was the Dalvik heap size.I doubled the default heap size to 256MB from 128MB that is the default. The Dalvik heap size adjusts how much memory a Dalvik VM instance can use. The more memory a single app can use, the less often Dalvik has to run through its garbage collection routines. This takes a load off the CPU and may be one reason my PE has seemed so much snappier. This may just be placebo, though. It shouldn't cause any harm and the PE has 512MB of RAM to play with so... worth doing, imo.

Code:
dalvik.vm.heapsize=256M
dalvik.vm.execution-mode=init:jit
I have had my PE running with a 256MB heap for 2 years with no issues and a few days with the JIT on and no problems. I made the same changes to my friends PE today and he hasn't had any problems, either.
It might be helpful if those of you who put up articles about changing files like build.prop, go through the steps of how to change build.prop for those fellow travelers who would like to benefit from these improvements but are a little bit nervous about how to actually implement them without turning their beloved PEs into the dreaded "brick"

Thanks, in advance...

Gerrye is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
build.prop performance tweaks (touch response, media save size, faster bootup etc.) multiprose enTourage eDGe 3 04-29-2012 09:16 PM
Dingo - Noticeable Performance Boost, 9 hour LCD and 20 hour Reader battery life?! borisb enTourage Archive 18 09-07-2010 11:52 AM
Increasing the font size when converting PDF Anonymouslemming LRF 4 05-28-2010 03:39 AM
Library size and performance MrFinch Calibre 4 01-01-2009 04:11 AM


All times are GMT -4. The time now is 08:37 AM.


MobileRead.com is a privately owned, operated and funded community.