About performance and memory usage

[Jack Lau]

Hello all,
If I use an object with a lot of getters and setters (e.g 100) instead of an object with just 1 getter and 1 setter, is it poor in performance and memory usage? (At runtime, only 1 getter and 1 setter will be called on each object).
Thanks,
Jack

[Dirk Schreckmann]

I don't understand your question.
Moving this to the Performance forum...

[Ernest Friedman-Hill]

I also have no idea what you're asking. Perhaps a little bit of code to illustrate how having one getter and 100 getters could be alternate implementations of the same class?

[stephan schweitzer]

Originally posted by Ernest Friedman-Hill:
I also have no idea what you're asking. Perhaps a little bit of code to illustrate how having one getter and 100 getters could be alternate implementations of the same class?

Alternative 1 (one getter/setter):

  
class A
{
 public int a1;
 public int a2;
 ...
}
class B
{
 private int a1;
 private int a2;
 ...
 A getA() 
 {
   A a = new A();
  
   a.a1 = a1;
   ...
 }
 void setA(A a)
 {
   a1 = a.a1;
   ...
 }
}

Alternative 2 (n getter/setter):

  
class B
{
 private int a1;
 private int a2;
 ...
 public int getA1() { ... };
 ...
 public void setA1(int a1) { this.a1 = a1; }
 ...
}

Not very clever and elegant perhaps (it depends on the context i think)
but these code fragments are alternative implementations for the same
class.
I think the question of Jack is if the number of methods of a class has
any impact to the performance. I think the number of methods influences
only the size of the class file (and so the time needed to load the class)
and the size of the vtable (but this should not influence performance).
I hope this helps
Stephan

[Jeanne Boyarsky]

Jack,
If the getters and setters are just getting/setting a field, there shouldn't be a performance difference. (or if there is it would be tiny)
However, the getters/setters are transferring data across a network, it is better to make one call. This happens in frequently in EJBs.