Comment #5 on issue 1323 by [email protected]: Publication status
update very slow for large collections
http://code.google.com/p/qubit-toolkit/issues/detail?id=1323
I timed the method calls within the processForm() method of the class:
apps/qubit/modules/informationobject/actions/editAction.class.php
And got the following numbers for the Alexander Cameron Rutherford fonds
with 127
descendants:
End collection type update: 0.030000 s
End object term relation update: 0.030000 s
End event update: 0.030000 s
End status update: 34.890000 s
End child level update: 34.890000 s
End save of info object id #334 at 77.710000 s
Finish form processing: 77.710000 s
The numbers for the "Government of Alberta" series within the fonds with 33
descendants:
End collection type update: 0.030000 s
End object term relation update: 0.030000 s
End event update: 0.030000 s
End status update: 11.500000 s
End child level update: 11.500000 s
End save of info object id #387 at 22.450000 s
Finish form processing: 22.450000 s
What's interesting is that the info object save took 3x longer for the
fonds, when I
would expect the numbers to be comparable. Is the info object save
recursively
saving descendants, and if so, why?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups "Qubit
Toolkit Issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/qubit-issues?hl=en.
