Optimization

Android Processing

darkgisba

in Android Processing • 2 years ago

What tips can you give me on code optimization for android.

I have been checking the memory usage of many games that are built with eclipse and they usually use from 15 to 30 mb of ram.

My game witch doesn't seems as complex as most uses 45mb and can ramp up to 80 and you can make it crash by repetitively jumping from level to level.

Im gonna give you some examples of code, that I think are giving me some performance issues.

void loadCoordinates() {
println("loaded"+""+millis());
try {
String[]strokesdone = loadStrings("\\turtle\\ownStrokes.txt");
for (n=0; n<nlvl;n++) {
ownstrokes[n] = int(strokesdone[n]);
if (ownstrokes[n]==0) {
ownstrokes[n]=int(10);
}
}
}
catch (NullPointerException e) {
String[] strokesdone = new String[nlvl];
for (n=0; n<nlvl;n++) {
strokesdone[n] = 10+"";
}
saveStrings("\\turtle\\ownStrokes.txt", strokesdone);
}
nMax=cX.length;
for (n=0; n<nMax;n++) {
hitX[n] = width/float(cX[n]);
if (float(cX[n])==0) {
hitX[n]=0;
}
hitY[n] = height/float(cY[n]);
if (float(cY[n])==0) {
hitY[n]=0;
}
}
}

that function is played at the start of most levels to reset coordinates for hitbox's and my memory usage ramps up at every new level.

void level26() {
if (load==0) {
nulify();
loadCoordinates();
die=0;
drag=0.98;
tinting=255;
H=height/24;
W=width/16;
posX=width/1.4;
posY=height/1.4;
dX=0;
dY=0;
glue=0;
bounce=0;
movement=2;
}
load=1;
image(level[lvl], 0, 0, width, height);
whirlCount=(whirlCount+0.2)%4;
image(whirl[int(whirlCount)], hitX[710], hitY[710], width/10, height/15);
//game maker stuff
if (nMax>0) {
hitX[nMax]=abs(hitX[nMax-1]-mouseX);
hitY[nMax]=abs(hitY[nMax-1]-mouseY);
}
character();
image(levelForeground[lvl], 0, 0, width, height);
ui();
//stuff to delete later
if (edit==1) {
for (n=682;n<711;n+=2) {
stroke(100);
fill(255, 80);
rect(hitX[n], hitY[n], hitX[n+1], hitY[n+1]);
fill(0);
text("square "+(n/2+1), hitX[n]+hitX[n+1]/2, hitY[n]+hitY[n+1]/2);
text("n "+n, hitX[n]+hitX[n+1]/2, hitY[n]+hitY[n+1]/2+10);
}
}
//stuff to delete later**
if (posX<W) {
posX=W;
dX*=-stone;
}
if (posY<H) {
posY=H;
dY*=-stone;
}
for (n=682; n<712;n+=2) {
if (colision2(posX, posY, H, W, hitX[n], hitY[n], hitX[n+1], hitY[n+1])==true) {
fill(255);
////////////////////bumpers//////////////////////
if (n==696||n==698||n==700||n==702||n==704||n==706||n==708) {
if (bump==0) {
dX=(width/32)*random(-1, 1);
dY=(height/48)*random(-1, 1);
bump=n;
break;
}
}
//speeed!!!!!!!!!!!!
if (n==690||n==692||n==694) {
dY++;
break;
}
////////////// PIT
if (n==684) {
dX=(hitX[n]+(hitX[n+1]/2)-posX)/50;
dY=(hitY[n]+(hitY[n+1]/2)-posY)/50;
die();
glue=0;
break;
}
// //glue tiles
if (n==634||n==632) {
glue=n;
stone=1;
}
if (dY>0&&posY<hitY[n]) {
posY-=dY;
dY*=-stone;
}
if (dY<0&&posY>hitY[n]+hitY[n+1]) {
posY-=dY;
dY*=-stone;
}
if (dX>0&&posX<hitX[n]) {
posX-=dX;
dX*=-stone;
}
if (dX<0&&posX>hitX[n]+hitX[n+1] ) {
posX-=dX;
dX*=-stone;
}
// // bouncy tile
// if(n==38){
// dX*=bounce;
// dY*=bounce;
// }
// win tile
if (n==710) {
//////////////
if (nstroke<ownstrokes[lvl]&&ownstrokes[lvl]!=0) {
ownstrokes[lvl]=nstroke;
String[] strokesdone = new String[nlvl];
for (n=0; n<nlvl;n++) {
strokesdone[n] = ownstrokes[n]+"";
}
saveStrings("\\turtle\\ownStrokes.txt", strokesdone);
}
nstroke=0;
/////////////
lvlcomplete[lvl]=1;
lvl++;
if (lvlcomplete[lvl]!=1) {
lvlcomplete[lvl]=2;
}
for (n=0; n<nlvl;n++) {
leveldone[n] = lvlcomplete[n]+"";
}
saveStrings("\\turtle\\setup.txt", leveldone);
load=0;
}
}
stone=0.8;
}
//bumper sistem
for (n=682; n<710;n+=2) {
if (colision2(posX, posY, H, W, hitX[n], hitY[n], hitX[n+1], hitY[n+1])==false&&bump==n) {
bump=0;
}
}
//glue system
for (n=614; n<640;n+=2) {
if (colision2(posX, posY, H, W, hitX[n], hitY[n], hitX[n+1], hitY[n+1])==false&&glue==n) {
dX=0;
dY=0;
}
}
}

Thats a example of how I do my levels and colision detection.

void imagetool() {
if (lvl==-2) {
if (menuloaded==false) {
menuloaded=true;
for (n=0;n<9;n++) {
menu[n]=loadImage("menu"+(n)+".png");
}
}
}
else {
for (n=0;n<9;n++) {
menuloaded=false;
menu[n].delete();
}
}
if (lastlvl!=lvl&&lvl!=-2&&lvl!=-1) {
level[lvl]=loadImage("lvl"+(lvl+1)+".png");
}
if (lastlvl!=lvl&&lvl!=-2&&lvl!=-1&&lvl!=48) {
levelForeground[lvl]=loadImage("lvl"+(lvl+1)+"Foreground.png");
}
if (lvl!=lastlvl) {
for (n=0;n<level.length;n++) {
if (n!=lvl&&level[n]!=null) {
level[n].delete();
}
}
for (n=0;n<levelForeground.length;n++) {
if (n!=lvl&&levelForeground[n]!=null) {
levelForeground[n].delete();
}
}
}
}

Thats how I handle images and image deletion to free up ram.

Please have a look at this samples and hopefully someone with a more experienced eye than I will find some obvious flaw with a piece of the code.

Thank you in advance.

PS , all my images are PNG, do you think thats the best file type ?

Replies(11)

elendilch

Hi
I've launched a topic pointing in this direction, too: https://forum.processing.org/topic/memory-allocation

I think nulling should be good, java garbage collector will do some work.

Yeah I think png is a good format, because the apk is rather small due to the png's conmpression.
However you have to be aware that every png you load, is converted into a bitmap.
So a completely black image 1000x1000 pixels is maybe 5kb in png but loaded its very big because every pixel is loaded.

However I have the suspicion that it might be a problem of processing or OPENGL (BTW which rendere do you use?).
As i described in my thread (link) I tested my game without images, and it still uses a lot of memory.
I don't understand why the heap memory is small and the memory usage (according to task managers) is high.

Maybe you should use ddms (debug monitor) and analyze the heap dump with eclipse memory analyzer.

darkgisba

Re: Optimization

2 years ago

It wont elendilch, iv tried nulling and it doesnt remove the image from memory even if you call the gc yourself.

randomimg.delete(); does remove the img from ram, and thats why i am using it.

Iv have tried soo many diferent things during these last 2 days, iv even commented out blocks of my code to try and identify the error , i used JVSM ( the java tool for heap checking and analysing) and i found that he PImage class usage is rocket high, soo I think something is wrong with either the way I use my images or with the way that the android does not clean that class.

Im gonna try using the eclipse functions to load and use images, because I use the mediaplayer and sounpool from android , and when I comment it out the performance is not improved.

This leads me to think that the eclipse classes are run onto separate threads to improve performance, and that might be why every game I see uses extremly small ram, even thought they have many images.

By the way, iv tried Opengl, a3d and a2d, and a3d works best, but they all consume the same amount of memory.

elendilch

Re: Optimization

2 years ago

I've noticed too, that PImage is very big (a subclass of processing.core.PGraphicsAndroid3D).
let me know if you have found something interesting.

darkgisba

Re: Optimization

2 years ago

Hi, i have been going around and around my code, and i now know that the memory usage is definitly due to the images.

Basicly, when I load the images they use for example 1mb of memory each, and untill they are displayed on screen they use 1mb only..

The problem lies with the first time you show them on the screen and it increases the memory by another 1mb.

I have tried not to use image(x,y,w,h) and used only x and y, because i thought the resizing was creating a duplicate, but the memory increase still happens.

Soo what I need to know is why doesnt the image take all the memory it needs when you load it, and how can I make it so?

By the way, the images im talking about represent levels, so I only use one at a time.

Basicly, i have a function that is deleting my PImages that are not used, and its freeing memory, but the "duplicate" that im telling u about stays on the memory and is not removed even when I call a gc.

Please help anyone!

th0ma5

Re: Optimization

2 years ago

I had some luck in not really "deleting" PImages, or calling GC manually, but rather continually reusing the instantiated PImage objects, and I'd find the upper bounds of the count of those by just loading the biggest of images in there until I ran out of the target ram. If I didn't want to show the image, I just didn't call draw... if I wanted to load other images, I had to call the loadImage into one of the existing PImage objects. I tried to do that loading inbetween main transitions of the software, and not during animation loops as that would cause pauses and such, or perhaps the GC thought that'd be a good time to run. Anyway, the problem isn't the images per se, it's the amount of image objects you can have at one time, but you can always put new images in the existing objects. I guess if you need more images at a time, think smaller images, or well, more ram. The amount of ram used should be roughly the uncompressed image size.

darkgisba

Re: Optimization

2 years ago

I apreciate the reply th0mas, but the reusing of Pimages is exactly what i was doing before and i still have the same problem..

Dont get me wrong, on the computer it works perfectly, but on the phones its oo limited, anyway tonight im going to try with vector graphics and see how it feels...

andres

Re: Optimization

2 years ago

Hey guys, I'm following this thread with attention, as these issues with memory usage in the P3D (A3D) renderer might be pointing to some problems in the code I wrote for texture handling.

One thing to keep in mind which could explain at least part of the increased memory usage in P3D, is that when you initially call loadImage(), the pixels array in the PImage object remains null. But when the object is drawn with image(), then the pixels array is initialized with a size of width * height so it can be used to copy the image to the opengl texture.

darkgisba

Re: Optimization

2 years ago

thx for all the replies soo far guys, and I found the fix, share this around if anyone else is having this problem.

levelForeground[n].resize(1, 1);

levelForeground[n].updatePixels();

levelForeground[n].delete();

Thats what I do after im not using a image anymore, the resize and the update remove the memory usage from the renderer( doesnt really remove but rather reduces it to 1kb or something);

And the delete removes the image file from memory.

This way everytime i use an image on screen, i can remove it later on and not suffer from out of memory errors.

To andres, you should try and implement something like this to the PImage class as a standard so that the images dont linger on the memory untill you exit the program.

Thanks a lot everyone for the inputs you gave, my game is now running 99% perfect.

thomas.di..

Re: Optimization

2 years ago

could try to run the following code please.
i usually use something like this if i want to make sure, ram gets freed. i set the object to null, and run the gc manuall (sam as described above) and usually it works.

in the following example, i create images (100 images, 1000px / 1000px) , which ends up with about 500mb of ram-usage, when pressing 'd' all the images are set to null, and the gc gets called... which ends up at 60mb of ram-usage:

import processing.opengl.*;
PImage img[];
void setup(){
size(100,100);
//size(100,100, OPENGL);
generateImages();
}
void draw(){
}
public void generateImages(){
img = new PImage[100];
for(int i = 0; i < img.length; i++){
img[i] = createImage(1000, 1000, ARGB);
}
println("\ngenerated images");
printMemoryUsage();
}
public void deleteImages(){
if( img != null){
for(int i = 0; i < img.length; i++){
if( img[i] != null){
//img[i].delete();
img[i] = null;
}
}
}
println("\ndeleted images");
printMemoryUsage();
println("\nfreeMemory()");
freeMemory();
}
public void printMemoryUsage(){
println("Total Memory "+ (Runtime.getRuntime().totalMemory()/sq(1024*1.0)) +" mb");
}
void keyReleased(){
if( key == 'd'){
deleteImages();
}
// if( key == 'f'){
// freeMemory();
// }
}
void freeMemory(){
Runtime r = Runtime.getRuntime();
float memoryUsed = Runtime.getRuntime().totalMemory()/sq(1024*1.0);
int countGC = 0;
//printMemoryUsage();
while (memoryUsed > 100 && countGC++ < 10){
r.gc();
memoryUsed = Runtime.getRuntime().totalMemory()/sq(1024*1.0);
}
printMemoryUsage();
} // end void freeMemory()

andres

Re: Re: Optimization

2 years ago

Things are different between Android and dektop. Anyhow, what version of Processing are you using with this code?

darkgisba

Re: Optimization

2 years ago

But the gc on the phone works differently than on the computer.

Top Reply

Optimization

Replies(11)

Re: Optimization

Re: Optimization

Re: Optimization

Re: Optimization

Re: Optimization

Re: Optimization

Re: Optimization

Re: Optimization

Re: Optimization

Re: Re: Optimization

Re: Optimization

Statistics

Tags

Actions