Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #29646 Back to Issue ]
Summary 0029646: Performance problem in add payment query
Revision 2015-04-21 10:11 by ioritzCia
Description There is a query that gets built in Add Paymen functionality that comes from the following hql to be injected:

select @selectClause@
from FIN_Payment_ScheduleDetail as psd
left outer join psd.orderPaymentSchedule as ops
left outer join ops.order as ord @joinClauseOrder@
left outer join ord.businessPartner as ordbp
left outer join ops.fINPaymentPriority as opriority
left outer join ops.finPaymentmethod opsfp
left outer join psd.invoicePaymentSchedule as ips
left outer join ips.invoice as inv @joinClauseInvoice@
left outer join inv.businessPartner as invbp
left outer join ips.fINPaymentPriority as ipriority
left outer join ips.finPaymentmethod as ipsfp
left outer join psd.organization as org
left outer join org.organizationInformationList as oinfo
left outer join psd.paymentDetails as pd
left outer join pd.finPayment as fp
@joinClause@
where @additional_filters@
and @whereClause@
group by @groupByClause@
@havingClause@

You can find attached a part of the postgres log with the resulting query its duration and parameters. In this case took more than 50 seconds.

This is not the usual time for this query in the log, postgres is configured in this instance to log the queries that are slower than 5 sec. An there are 3503 appearances of that query that were slower than 5 sec since 03-02-2015 to 13-04-2015. The usual time the query takes when it appears in the log is from 6s to 10s, which is still slow, but there are times when it takes more.

We have a cloned instance.

Revision 2015-04-21 10:09 by ioritzCia
Description There is a query that gets built in Add Paymen functionality that comes from the following hql to be injected:

select @selectClause@
from FIN_Payment_ScheduleDetail as psd
left outer join psd.orderPaymentSchedule as ops
left outer join ops.order as ord @joinClauseOrder@
left outer join ord.businessPartner as ordbp
left outer join ops.fINPaymentPriority as opriority
left outer join ops.finPaymentmethod opsfp
left outer join psd.invoicePaymentSchedule as ips
left outer join ips.invoice as inv @joinClauseInvoice@
left outer join inv.businessPartner as invbp
left outer join ips.fINPaymentPriority as ipriority
left outer join ips.finPaymentmethod as ipsfp
left outer join psd.organization as org
left outer join org.organizationInformationList as oinfo
left outer join psd.paymentDetails as pd
left outer join pd.finPayment as fp
@joinClause@
where @additional_filters@
and @whereClause@
group by @groupByClause@
@havingClause@

You can find attached a part of the postgres log with the resulting query its duration and parameters. In this case took more than 50 seconds.

This is not the usual time for this query in the log, postgres is configured in this instance to log the queries that are slower than 5 sec. An there are 3503 appearances of that query that were slower than 5 sec since 03-02-2015 to 13-04-2015. The usual time the query takes when it appears in the log is from 6s to 10s but there are times when it takes more.

We have a cloned instance.



Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker