I assume that you've tried bumping up -Xmx. Does it seem to
progress further when you do that? Can you tell how far it got?
The amount of memory required should map to the size and
complexity of the schema. I can't really check for
traditional memory leaks because the object hierarchy, by
design, grows as it gathers more information.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi - I ran a test yesterday against the schema that was
failing previously (which has been 'augmented' over time to
currently 5018 tables). Under the same conditions
(Xmx=1584m) version 3.1 successfully completed. I am also
under the impression that there was a speed enhancement,
however I don't have an actual record of run times under
controlled conditions to prove it.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A fair number of tables, say 60% or so are 'achival' without
FKeys and the like. Still it is pretty nice to be able to
get a schema map on this.
I was thinking the other day that it would be nice to have a
flexible filtering mechanism, perhaps in the form of a java
class that could be picked up via a plugin mechanism.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Interesting idea. You *might*, however, be able to do what
you're looking for with a regular expression (specified with
-i). I'm no regex guru, but it should be possible.
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1264584
I assume that you've tried bumping up -Xmx. Does it seem to
progress further when you do that? Can you tell how far it got?
The amount of memory required should map to the size and
complexity of the schema. I can't really check for
traditional memory leaks because the object hierarchy, by
design, grows as it gathers more information.
Logged In: YES
user_id=1264584
If this bug was opened by Amihay
(http://sourceforge.net/forum/forum.php?thread_id=1457002&forum_id=462850)
then it's probably already been resolved.
Logged In: YES
user_id=1264584
This should be fixed in 3.1.0. Let me know if it isn't.
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Logged In: NO
Hi - I ran a test yesterday against the schema that was
failing previously (which has been 'augmented' over time to
currently 5018 tables). Under the same conditions
(Xmx=1584m) version 3.1 successfully completed. I am also
under the impression that there was a speed enhancement,
however I don't have an actual record of run times under
controlled conditions to prove it.
Thanks!
Logged In: YES
user_id=1264584
It's amazing that it actually worked with over 5000 tables!
John
Logged In: NO
A fair number of tables, say 60% or so are 'achival' without
FKeys and the like. Still it is pretty nice to be able to
get a schema map on this.
I was thinking the other day that it would be nice to have a
flexible filtering mechanism, perhaps in the form of a java
class that could be picked up via a plugin mechanism.
Logged In: YES
user_id=1264584
Interesting idea. You *might*, however, be able to do what
you're looking for with a regular expression (specified with
-i). I'm no regex guru, but it should be possible.
John