These are chat archives for inveniosoftware/invenio
webcollon invenio1.x gets excessively slow even though we did not add new collections? and even better, are there some counter measures?
webcoll -u admin -f --profile cumulativeand then look in the corresponding
100:%because then the query to get latest 10 records could take many seconds. You can check your regular webcoll task log to see whether you don't have some long-taking collections as bottlenecks. (3) Finally, note that you can also profile one single collection only, e.g.
webcoll -u admin -c Books -f --profile cumulative, which may provide additional insight.
-980:"DUMMY" -980:"DELETED". But that should be pretty fast to run... you can check in ipython. If the home collection is the problem, then I assume it does not have any dbquery defined, and only collects hits from its daughter collections? That would not be it then. You can try to run only the record gathering part (without I18N cache creation part) to see, for example
webcoll -u admin -f -c Atlantis Institute of Fictive Science -p 1 --profile cumulative
-980...stuff in the code and yes, you're right, the collection does not have any dbquery defined. when I test the search for deleted records in ipython I do not see any bad performance either. I'm checking the cache updates now.
current_useris not available in the API app? (Invenio 3)
inv $ib/webcoll -u admin -p 1 -f -c PUBDBgives me
2016-04-19 11:21:09 --> Task #166444 started. 2016-04-19 11:21:09 --> PUBDB / reclist cache update 2016-04-19 11:28:23 --> Task #166444 finished. [DONE]
-cand observe the time spent for each daughter collection with
-p 1mode switched on. The bottleneck really depends on your collection tree setup and your collection dbquery definitions, so I'm just posting some general thoughts on where to look...
980__c:DELETEDcauses a lot of substraction operations that consume the time?
webcoll -u admin -f -p 1to see where the seconds are spent... would be probably with one of daugther collections. I doubt it's the home collection.
Invenio-Records-UInow stable again? I’ve seen the new releases
elasticsearch-py. Is there an easy way to drop to the wrapped library and use that instead?
cursor.py(mysql) but I'm not sure this is a helpful result.
ANALYZE SELECT ...on your slow queries to see whether there is a bottleneck there. You can also run
mysqltunerto see whether you can spot some potential for optimisation there. E.g. have you introduced tmpfs for MySQL in-memory tables? They are used quite a lot for bibxxx queries... See http://tiborsimko.org/mysql-tmpfs.html for inspiration.