c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Sunday 30 January 2011, you wrote:
> ** Attachment added: "stock_logs.txt"
>   
Is that log suggesting that you have hundreds of stock locations? How come?

I don't claim that there is any "invalid" or "oversize" number for any of the 
ORM tables, but production examples of sizing will help us to take better 
design decisions about the internals.
For example: (fictional) we think "ok, a partner may have 2-3 different 
adresses, let's not worry to optimize loops out of partner->address 
matchings". And we write simple python code about that[1]. Then, some 
production database comes over with 4000 adresses on one partner. And, of 
course, performance suffers there. Hence your "bug".

Giving us simple statistics, like "I have setup a supermarket database with:
 - 5000 products
 - 18000 pricelist entries
 - 40 warehouse locations and 1200 shelves
 - 120 employees
 - 50 accounting journals
 - 2000 cash moves per day..
 - expected printing of POS invoices in <2sec
 - ...
" 
will help us do dimensioning analysis. Perhaps not only us, but even yourself, 
to setup a testing system that will catch common pitfalls before deploying on 
a customer.
I'd be glad to assist anybody that tries to setup such a testing system 
(infrastructure, I would call it).


[1] that's a common practice from people that think Python, Java, Ruby can be 
fast languages, compared to SQL.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/704394

Title:
  [6.0] dashboards display intempestively after you started navigating

Status in OpenERP Web Client:
  Opinion

Bug description:
  This is web client rev #4386 with a real production database (over 10
  000+ orders/expeditions). It happens that on this database with real
  data, dashboards are rather slow to appear (I hope I'll be able to
  report an other bug about that poor performance, mostly visible in
  sale and stock dashboards).

  So, a natural behavior from the user, is to start navigating using the left menu while the dashboard is stuck.
  The user may start clicking on the left menu elements and would expect the central content will display accordingly to those left menu choices.

  Still, this is not the case: a few seconds later, when the dashboards
  is finally ready to load, the dashboard will display in the central
  content, no matter your navigation choice, this is a rather confusing
  user experience and very time consuming as it force you to wait
  forever for the dashboards to load for almost any trivial operation.