Ancestris - very long duration for the linking in GEDCOM

[Pollux]

If I set the protocol quality to OFF in the Ancestri's preferences (no indication of its influence on the time), my GEDCOM will be read in within an acceptable time!
This is followed by a very, very, very long duration for the linking.
Is there an explanation?

[FredericL]

Hi Pollux,

What do you call the "protocol quality" please ?

Cheers,
Frederic

[Pollux]

Moin Frederic,

Unfortunately, your question is not clearly translated by the translators.
I'll attach a screen shot.

Greetings,
Pollux

[FredericL]

Hi Pollux,

OK. This is the log detail.

The linking should not be very long if the loading is quick.

I would need to see the log but you would have to put it back to INFO level first. This should not affect the timing since very little information is displayed in that level.

Can you please do that and send me your log file please ?

Another question : did this happen suddenly or have you had the issue forever ?

Best regards,
Frederic

[Pollux]

Moin Frederic,

i will do this as soon as i am at my main computer.

I had the problem with the long link duration from the start. However, in the meantime I had also set the log quality to ALL.
In the preferences, there is no warning or reference to the extent to which these settings affect the loading time (including the link) of Ancestris.
Is it possible to display a factor here for each setting?

I really want to work with Ancestris and then recommend it to others.

What other logs etc could be helpful in analyzing the problems? Some may only be displayed if you want to (and know about it!), Others may not even be copied?
Or are ALL relevances in files?

Best regards,
Pollux

[FredericL]

Thanks Pollux,

We will take it step by step but I do want to get to the bottom of it !

The display level in the log only affects from FINE and below. Really no impact between OFF and INFO.

I recall you have lots of individuals in your Gedcom. How many again ?

What most affects the loading time is the available memory for the Ancestris java application. Send me also your .ancestris/etc/ancestris.conf file please.

Talk to you soon,
Frederic

[Pollux]

Moin Frederic,

Thanks for your participation!

Yes, proceed point by point, that is a good decision!

Zurga had already told me which OpenJDK is required or optimal for Ancestris, but please repeat:

# Check before / when starting Ancestris for:
- Optimal memory setting for Ancestris Java program
- Ideal version of OpenJDK = minimal + optimal (instead of Java)

There are over 333,000 people in my GEDCOM.
There is definitely rubbish (in between) that has to be 'disposed of'!
After many imports from the most popular genealogy programs in the world, old and new, this is definitely necessary!
I believe Ancestris has the tools to help me do this!

Ancestris
- Quick mode (especially for beginners / switchers))
- mobile version (for on the go + tablet = general start in quick mode)?
- Dynamically load 'modules' or plug-ins - unload

As soon as I use my desktop again, I note the processing (load, linking) times of my GEDCOM by Ancestris and send you the data you want.

Regards,
Pollux

[FredericL]

Hi Pollux,

Zurga is the best to know the configuration you need so we will stick to what he said.

What I know is that I have opened in Ancestris a gedcom file including more than 600 000 people with an 8 year old computer and 4G of RAM and the regular java 1.8 version. So the size of the Gedcom and the memory could be an impacting factor, but you should not have such an issue with the config and should not worry too much about searching the ideal settings.

Unless your gedcom has got a lot of information for each individual, and assuming Ancestris is the main application using the CPU and the computer was rebooted fresh, we should be ok to at least open the file.

I will wait for the first elements (the log INFO level and conf files). Make sure you delete all log files in the directory, so we know for sure it will be the right one.

Best regards,
Frederic

[Pollux]

Moin Frederic,
please have some patience.

So that you can see how much work I still have to invest in correcting my GEDCOM, I am sending a screen shot of the Trenton list of places.
Trenton doesn’t even appear very often in my GEDCOM, but in different forms.
So it is surely correct to select 'empty jurisdiction' (i.e. a place) for locations in the Ancestris preferences, right?

Best regards,
Pollux

[FredericL]

Hi Pollux,

Not sure where the 'empty jurisdiction' is in the Ancestrisd preferences.

If you want to harmonize places names though, the Best way is to use the List of Places view.

Best regards,
Frederic

[Pollux]

Moin Frederic!

Wow - I took a quick look at the list of places in Ancestris and the options from there!
Other options in other areas too - they're fantastic!

If Ancestris were better suited for beginners or those switching, it would be unreservedly recommended - even if I couldn't use it for daily (normal) use myself!

... if it weren't for this very long linking phase.
I have not forgotten what you need from me to analyze them! The data is still to come!

Ancestris is apparently modular, so should it be possible to use a minimal Ancestris (individually) for special purposes?

But I (now) noticed something in connection with _LOC (not in the Ancestris vocabulary).

After importing "Genealogy 'Kennedy'" into Ages! I read this GEDCOM with Ancestris.
The import to Ages! worked, but after reading in with Ancestris there is suddenly a list of places (_LOC) that are not assigned to any person.
I chose East Boston as an example.

Pollux

EDIT: _PLACE to _LOC
EDIT: + ScreenShot does not work, so posted as an 'answer'!

[Pollux]

Message in Ancestris: ... not assigned.

[FredericL]

Hi Pollux,

The gedcom has been altered by Ages which has changed locations into entities, but Ages has not adapted the tag names. This is not part of the Gedcom vocabulary hence the "?".

Ancestris can open any Gedcom and show you the anomalies, but it does not fix all gedcom errors. In this case, Ancestris no longer knows how to interpret the _LOC entities.

If you give me a file coming from Ages, maybe I can try to develop a conversion mecanism back to official Gedcom format.

Best,
Fredeeric