[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [geclipse-dev] Job Status
|
Hello,
Actually several million instances of GridJobStatus are potentially
created during one execution. By consequence, from my point of view it
is better to manage their life-cycles and reuse the old instances.
Furthermore it is not a lot of work to do.
Rom.
Mariusz Wojtysiak a écrit :
Hello!
Yes, at least a new JobStatusUpdater is created for each new Job, not
a Status itself as far as i see. But for sure Mariusz and/or Pawel
will have a more authoritative answer.
For every GridJob, which status can change (!= DONE, ABORTED, PURGED)
we create JobStatusUpdater object. But those objects are reused during
every status update for given job.
As Romain suggested, in fact: after every status update we create new
GridJobStatus object.
But I'm not sure that IGridJobStatus implementations causes problem
with garbage collector. Before changing strategy of creation
IGridJobStatus objects I suggest to start profile tool and check which
classes causes problems for GC.