SOAP mc_project_get_issues: performance improvement

[Marsso]

Hello,

We integrate MantisBT 2.18 with other tools. These tools use the SOAP API with 'mc_project_get_issues' method and the following parameters:

Code: Select all

<man:mc_project_get_issues soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <username xsi:type="xsd:string">XXXX</username>
    <password xsi:type="xsd:string">XXXX</password>
    <project_id xsi:type="xsd:integer">394</project_id>
    <page_number xsi:type="xsd:integer">1</page_number>
    <per_page xsi:type="xsd:integer">200</per_page>
</man:mc_project_get_issues>

But we noticed that response times was too high for a common usage with the third-party tool. The response time of the example above are about 8 minutes.

To detect where the loss of time might occur, we used an Application Performance Monitoring tool. We identified that several requests was done and take a few milliseconds each. So the response time is due to the amount of requests or the data processing.

We think the response time is related to the number of notes, attachments of each issues, but we can't check.

Is the problem known ? What are the possible reasons ?
Is there a way to decrease the response time of this method by tuning in configuration files ? or in the server configuration ?


For information the database sizing is about :

• mantis_bug_file_table (18K lines) 3.8 Gib
• mantis_bug_history_table (310K lines) 24 Mib
• mantis_bug_revision_table (20K lines) 7.6 Mib
• mantis_bug_table (20K lines) 3.4 Mib

Regards,

[atrol]

we used an Application Performance Monitoring tool.

This might be a database but not an application performance issue. Contact your database administrator to find out if / which statements are stressing the server.

Also interesting the length in bytes of the response. Fetching 200 issues can become quite a lot of data if the issues contain lots of notes, relationships, custom fields, ...

[Marsso]

We enabled the query logging of MySQL to find which statements could stressing the server : when we call the 'mc_project_get_issues' method, 2400 statements are executed. Each of queries lasting between 10 ms and 1 sec.

We continue to look for a way to improve the database / query performance, but we will have to disable temporarily the integration with the third party tool.

I'll keep you informed if we find a way to improve this.
Thanks for your reply !