Time response publishing in 6.4.0

Gerard_La Foneria

Dear all,

We’re using version 6.4.0 and we’re experiencing some troubles with the publication time response of the resources. I put you an example and later on Adrian (@pricua) will add the log with that example (ID1959): time publishing that single object exceeds 2:30 minutes. If we only publish level 1, time publication works correctly, but if we want to publish the second level, time is too long. In some other cases we have longest time responses.

We know that publishing a single ID publishes also relations, but continuing with this example, in this case (ID1959), have only around forty-five relations.

If that helps, we’re deducing that this happens in resources (ex. publications has the same problem), but this does not happen when publishing keywords from thesauri.

And probably linked to this issue, it seems that pop-up indicating publication process does not send the information from the API correctly because we can see data published in the API, but the emerging window continues indicating that’s still publishing.

Alex

As I see, you are publishing tch1, in the log any error appears therefore, it seems everything went well, but the publication takes a long time with 2 level resolution.

For the time of the resolution:
Could you see how many objects has related Material -tch57 field of the object ID1959?
And in Technique - tch168?

Usually the categories Material and Technique in thesauri are related to multiple objects, if you want to solve the 2 levels in publication, Dédalo will solve it:

the object -level 0
the thesaurus term -level 1
thesaurus term relations (all other objects related to the term)-level 2

For ex: if the material (plastic, ceramic, etc) has 500 hundred objects associated with it, with 2 levels, Dédalo will need to resolve the 500 hundred objects.

Gerard_La Foneria And probably linked to this issue, it seems that pop-up indicating publication process does not send the information from the API correctly because we can see data published in the API, but the emerging window continues indicating that’s still publishing.

Yes, as I said, publication process still publishing the related objects.

Best

pricua

This is the process log that is stored in the server's sessions directory.

{"msg":"Procesando... por favor espere"}
{"msg":"Procesando","counter":0,"total":1,"current":{"section_tipo":"tch1"},"total_ms":31.225,"errors":[]}
{"msg":"Procesando","counter":1,"total":1,"current":{"section_tipo":"tch1","section_id":"1959"},"total_ms":31.225,"errors":[]}
{"msg":"Procesando","counter":1,"total":1,"current":{"section_tipo":"tch1","section_id":"1959","time":123339.765},"total_ms":123370.99,"errors":[]}
{"msg":"Procesando","counter":1,"total":1,"current":{"section_tipo":"tch1","section_id":"1959","time":123339.765},"total_ms":123370.99,"errors":[],"memory":"3019 MB"}
{"result":true,"msg":["OK. Request done successfully"],"errors":[],"memory":"3019 MB","last_update_record_response":{"result":true,"msg":["Record updated section_id: 1959. Number of references: 49 in levels: 2"],"errors":[],"class":"diffusion_mysql"},"time":"2.057 min"}

The server has 32GB of ram and 16GB allocated to php

Manuel Gozalbes

I've checked the relations of the record ID 1959 and the time seems fine taking into consideration the thesaurus term relations when publishing with two levels. With the Id1959, the server has to check thousands of records:

Name of the property: 243 objects
Typology: 200 objects
Material: 4426 objects
Technique: 1731 + 317 objects
Period: 6372 + 4379 objects

So, it seems normal to last 2.30 minutes to check and publish 17.668 objects.
In fact seems very fast!!!

Thank you

Alex

Wow! 17.000 records are not a few... Maybe Speedy Gonzales, Mighty Mouse or Road Runner can go much faster...

With this number of relations, it makes sense that the publication takes 2 min and uses 3019MB of memory.

And I'm thinking that is not necessary use 2 levels always (or more, it is possible to set like 3 or 4 levels, but the time will be exponentially longer), maybe if you want to ensure that som complex and deeper relations will be published. but at those cases, you ca plan it, group the objects to be published and use night of weekends, etc.

Note: In the log Dédalo said that the main object id 1959 has 49 references, they are ONLY the main relations of the object, not the 2 level relations.

Best