Reduce desktop application memory

[major]

I'm developing a windows desktop (standalone) application which runs as an endless loop.
Once the application starts, a database connection is created (java.sql.Connection) and is used all over the application.
The loop does the following operations:
* Call web services
* Execute Sql queries to read data from Database
* Write image (downloaded by one of the web services) to disk. (approximately ~80KB)

My application takes about 50 MB memory.
How can I reduce my application memory usage?

[JosAH]

My application takes about 50 MB memory.
How can I reduce my application memory usage?

Why? An ordinary desktop has +- 1.5GB available for a user process; your process uses about 3 % of it ...

kind regards,

Jos

[lovelesh]

My application takes about 50 MB memory.
How can I reduce my application memory usage?

Its near to impossible to tell how to reduce the memory without looking at the code. A proper review would be required to tell something.

However, make sure you are:
1. creating objects only at the point of their requirement.
2. finalizing the objects as soon as their need ends.
3. handling writer objects properly.

[DarrylBurke]

2. finalizing the objects as soon as their need ends.

What?

db

[Tolls]

I'm developing a windows desktop (standalone) application which runs as an endless loop.
Once the application starts, a database connection is created (java.sql.Connection) and is used all over the application.
The loop does the following operations:
* Call web services
* Execute Sql queries to read data from Database
* Write image (downloaded by one of the web services) to disk. (approximately ~80KB)

My application takes about 50 MB memory.
How can I reduce my application memory usage?

As Jos says, this is a pretty small app anyway.
But that aside, shrink Xmx to the amount you want your app to fit in (something we cannot say, but you appear to have a size requirement). See if it crashes. Take a heap dump on an OOM exception and analyse it to see what was using the memory at the time of the crash. See if you can somehow reduce that. if not then you'll need a larger memory footprint.

[lovelesh]

What?

db

I mean nullify the reference variables so that referenced objects become candidates for garbage collection.

[DarrylBurke]

If variables are declared in the correct scope, it's virtually never needed to null them explicitly.

db

[lovelesh]

If variables are declared in the correct scope, it's virtually never needed to null them explicitly.

db

I completely agree to this.

[major]

Thank you guys