c2c-oerpscenario team mailing list archive

[Raphaël Valyi - http://www.akretion.com <704394@xxxxxxxxxxxxxxxxxx>]

@xrg,


1) We see sale and warehouse dashboards being the major performance
bottleneck in nearly all our 5 V6 deployments, not only this particular case
which as indeed some 1 000 locations (an online bookstore managing supplier
and customer consigned sales).

2) I insist, here my report is not only about only the slowness. But it's
also about the fact the user cannot skip the dashboard display: even if he
starts navigating away from that back hole, minutes after the dashboard is
finally ready, his navigation will be destroyed and bring back to those
useless dashboard, making web-client almost unusable in practice until you
edit those dashboards to drop their content.

3) I think you can look with Olivier Laurent: one of your 2nd level
migration customer you just migrated just facing this issue on v6 and you
have the database so you can study it.


On Sun, Jan 30, 2011 at 2:58 PM, Ferdinand @ Camptocamp <
704394@xxxxxxxxxxxxxxxxxx> wrote:

> well - IMHO the dashboards in web client should (and can ) be disabled -
> these are visual  gimmicks of no real use in day2day work - at least I
> know nobody who wants to see these statistics evertime he/she changes
> form accounting to sales and back.
>
> All these boards seem not to take into account company_id. Hence these
> reports show data of ALL companies even if the users has no access rigths to
> these companies (hopefully I am wrong, but I do not see any domain
> restriction)
> BTW the most efficient way to restrict the access is to rewrite/extend the
> underlying views and NOT using (unnecessary) domains
> I must admit, that I didn't examine how to pass uid and/or company_id to
> these queries.
>
> If someone wants to open dashboards he will do it.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> 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.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/openobject-client-web/+bug/704394/+subscribe
>

-- 
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.