Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7458793
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T13:30:01+00:00 2026-05-29T13:30:01+00:00

I have a bunch of classes that i have to tweak for improved memory

  • 0

I have a bunch of classes that i have to tweak for improved memory usage in exchange for CPU time, and i have junit 3 as a test framework to prove it.

While i can easily do that (use string.getBytes("UTF-8"); stuff multiple booleans in a byte, use long instead of Date, implement my own collections etc), I don’t really have a solid way to show improvements when i commit the code, because of the impredictable nature of the Garbage Collector.

When i am talking about collecting garbage, i mean i have done both of these 2 things: called System.gc(), AND tried to allocate an array like so long[] longs=new long[Integer.MAX_VALUE];
These are a few algorythms I tried to implement without success:

1:

a:garbage collect;

b:get the ammount of memory used at this moment; (long beforeold=Runtime.getRuntime().maxMemory - Runtime.getRuntime().freeMemory(); )

c:allocate an array of a few tens of thousands of instances of my old class;

d:garbage collect;

f: long afterold=Runtime.getRuntime().maxMemory - Runtime.getRuntime().freeMemory();

g:repeat the process instantiating the new classes

h:compare the differences in memory.

The results i got were freaking weird:
My “afterold” was less than my “beforeold” indicating some kind of weird garbage collecting event occured during memory allocation for the new classes.

The memory used by the new class instance turned out results anywhere from negative, to positive, signaling again some weird garbage collecting in the middle of instantiation.

Now, has anyone else tried to prove some classes are more efficient than others like this? It’s a very cool problem, but it’s still a problem.

Thx, you guys rule!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T13:30:02+00:00Added an answer on May 29, 2026 at 1:30 pm

    Heinz Kabutz has some tips in Java Specialists newsletter: http://www.javaspecialists.eu/archive/Issue193.html:

    public long calculateMemoryUsage(ObjectFactory factory) {
      Object handle = factory.makeObject();
      long memory = usedMemory();
      handle = null;
      lotsOfGC();
      memory = usedMemory();
      handle = factory.makeObject();
      lotsOfGC();
      return usedMemory() - memory;
    }
    
    private long usedMemory() {
      return Runtime.getRuntime().totalMemory() -
          Runtime.getRuntime().freeMemory();
    }
    
    private void lotsOfGC() {
      for (int i = 0; i < 20; i++) {
        System.gc();
        try {
          Thread.sleep(100);
        } catch (InterruptedException e) {
          Thread.currentThread().interrupt();
        }
      }
    }
    
    public void showMemoryUsage(ObjectFactory factory) {
      long mem = calculateMemoryUsage(factory);
      System.out.println(
          factory.getClass().getSimpleName() + " produced " +
              factory.makeObject().getClass().getSimpleName() +
              " which took " + mem + " bytes");
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Let's say I have a bunch of classes that look something like... class Foo{
In my program, I've got a bunch of classes that will only ever have
I have a web application that contains a bunch of classes in the App_Code
I have a bunch of classes that I intend to serialize in order to
We have a bunch of classes that listen for events from the server and
I have a bunch of classes that have a set of dependencies. Dependency Injection
I have a bunch of classes that each read in their values from an
I have a bunch of classes that all contain a Shared ReadOnly Dictionary. If
I have a bunch of stored, serialized classes (that all inherit from a base
I have a bunch of classes that each have a property called Sequence. This

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.