openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #07363
[Bug 723352] Re: Performance tuning: invoice analysis' postgres view doesn't scale
Hi, Whether or not you change something in 6.1, 6.2 The bug I initially
reported IS valid. So please do not mark the bug as invalid. The
dashboards do not load whatsoever in larger databases. I have seen this
in at least 3 installations and it is a problem with the views. They do
not load. You have to delete the dashboards completely for the web
client to even function. You say it is the most important view in your
opinion, but consider me working with several enterprise class business
and them never once seeing the dashboards because simply, they do not
function.
Lets also consider that OpenERP 6.0 is an LTS version, which I think
many people have not considered by fixing bugs in new releases but not
fixing them in the long term supported version
In the databases that I work with, you cannot select even 100 rows from
sale_report without > (30 second) delay in query time
--
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/723352
Title:
Performance tuning: invoice analysis' postgres view doesn't scale
Status in OpenERP Server:
Invalid
Bug description:
On a new database Postgres views work great. Especially in web client
which is a primary feature of the web client. The dashboards. However,
over time or if you are a large shop and import many older orders and
products the queries do not return in a reasonable amount of time and
the clients time out before they can run. For instance, prime example,
This is a database query generated by the program
SELECT "account_invoice_report".id FROM "account_invoice_report" WHERE
(account_invoice_report.year ilike E'%2011%') AND
(account_invoice_report.user_id = 1) ORDER BY date desc
On my database, which has 5,000 products and 10,000 orders, not even
current but older data. It takes more than 700,000 ms to return this
query. In this case it is never possible to use the web client or any
of the views because the query does not return. I believe that the
views have to be reworked to be useful in any environment that is a
medium sized company.
A little more information, I have no database mods, or special changes
of any kind. I have a clean database with latest sources. I believe
most of the views, if not all suffer from this issue. Consider the web
client that heavily depends on postgres views is not usable in this
condition. Please confirm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/723352/+subscriptions