We are getting some perfomance issues and I would like some recomendation, help, … whatever.
The problem is a slow response from Tamino in cases that apparently it should not happen. Lets use as reference the following query (the field STLRecordSort is indexed):
…_XQL=STLHoldingIbermarc sortby(STLFields/STLRecordFields/STLRecordSort asc)&_encoding=windows-1252&=&_cursor=open&_position=1&_quantity=10
Just started the DB server, the previous query takes around 60 seconds. I see as the buffer pool usage increase until 90MB, before getting response. Next try with the query, the answer is near to instantaneous. Related queries against the same Doctype, works fine or badly, according to previous requested queries.
I have the idea that, the buffer pool performes some kind of query catching, but I have no idea of the reaching.
May be (this is a supposition) the former queries are penalized translating to RAM indexes, and other Tamino resources, in order to reach a reasonable response rate after some first accesses to the DB.
My question is then, how should we check such response performance. Or if it is reasonable expect ‘performance fails’ in the first steeps of the application running, and then, hopefully, resources will be reasonable balanced to provide reasonable answer.
May be the problem is another and we have any other reason of poor perfomance than the one I am presuming.
The execution context is:
- 4GB RAM
- Tamino 126.96.36.199
- Buffer pool 600MB
- Around 1.000.000 records in the previous Doctype
- Records are around 4KB except a few (300) that are around 100 KB.
If useful, the schema is atached.
Thanks for any feedback
ibermarcstorec.tsd (226 KB)