[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipselink-users] memory usage
|
Because our application is built in terms of JPA Objects. This is a
small part of our app, a data conversion from another version of our
system. Your response is almost like asking why I didn't write it in
perl...or maybe that is what you are suggesting?
On Oct 19, 2009, at 5:52 PM, Tim Hollosy wrote:
I don't have a good answer, I'm just curious as to why in the world
you'd want to use JPA for this sort of job?
./tch
On Mon, Oct 19, 2009 at 5:51 PM, David Parker <dap@xxxxxxxxxxxxxxxxxxxx
> wrote:
I am running a long data import that uses eclipselink 1.1.2 for
persistence.
I see memory increasing slowly but surely as it goes along. The
YourKit
profiler does not identify anything as a link, but I do seem to
have an
increasing "retained size" for
org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork
[Stack
Local]
I see there is a clear method on TransactionWrapperImpl, but that
does not
seem to be in the JPA EntityTransaction API.
Is there a best practice for long running data imports? Should I be
clearing
something?
Thanks.
=============================================
David Parker
dap@xxxxxxxxxxxxxxxxxxxx
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
=============================================
David Parker
dap@xxxxxxxxxxxxxxxxxxxx