Tryton - Issues



Title Slow open or can't open tree view
Priority feature Status resolved
Superseder Nosy List ced, jesteve, pokoli, resteve, reviewbot, roundup-bot
Type feature request Components sao, tryton
Assigned To ced Keywords review
Reviews 44641002,44021002
View: 44641002, 44021002

Created on 2015-07-29.15:36:04 by resteve, last changed by roundup-bot.

New changeset 94b953679fe4 by Cédric Krier in branch 'default':
Use limit to expand tree
New changeset f6cccbf4aa44 by Cédric Krier in branch 'default':
Use limit to expand tree
review44021002 updated at
review44641002 updated at
msg38510 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2018-02-20.17:24:25
Here are review44641002 and review44021002 which implement this behavior.
msg38507 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2018-02-20.16:43:22
Indeed instead of creating a tree_open action on client side which is complicated and may not be a good result. I think it is better to just switch to the form view. Normally the form view should always contain the list of children. This One2Many should not be an performance issue to load as it is a list (not a tree) so the loading will be done on the fly.
msg38501 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2018-02-20.15:50:34
I think we could have the tree_open action from msg22391 implemented automatically on the client side when the size of children is too high.
msg22392 (view) Author: [hidden] (resteve) Date: 2015-09-16.17:22:00
> You could use the tree_open action on a list view to open a second list view with the children etc.

It's an idea. I try it. Thanks
msg22391 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2015-09-16.17:00:05
For me, it makes no sense to use a tree view for such large amount of data.
You could use the tree_open action on a list view to open a second list view with the children etc.
But definitely, we can not limit the number of children record displayed in a tree view because it is the value of a one2many which should keep integrity and so keep it real value.
Anyway, such large treeview are neither useful to the user as it is impossible to understand any information in such noise.
msg22034 (view) Author: [hidden] (resteve) Date: 2015-07-29.17:08:31
> So can you explain where is the bottleneck?

In tree view (not list), click a parent record and show a lot of records (childreen).

> In the server? In the client?


> Difficult to do anything without more information.

Tree view can't show a lot of data.

@sergi: you could render a BABI report and try navigate a tree view and lot of records. A BI report for example: all products salable in third months and subdivision (it's an example).

(All) <- click and impossible to render client a lot of data.
 - Product 1:
  - Barcelona: 34
  - Madrid: 10
 - Product 2:
  - LLanguadoc: 56
  - Perpinyar: 10
 - Product 10.000:
msg22033 (view) Author: [hidden] (pokoli) (Tryton committer) (Tryton translator) Date: 2015-07-29.16:46:58
So can you explain where is the bottleneck? In the server? In the client?
Difficult to do anything without more information.
msg22032 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2015-07-29.16:27:09
This is not a feature and barely a wish.
msg22030 (view) Author: [hidden] (resteve) Date: 2015-07-29.16:08:21
> I don't know what you are expecting

User is waiting to show childreen data. For example:

- First level: 1 row <- User click this arrow to show second level.
  - Second level: User waiting to show 27thousand records. Second level don't have function fields; only m2o and char.

It is impossible to work tree view with a lot of records. GTK client doesn't crash. GTK client can't render big data.

An idea to solve this scenario is not show all records; only show some records and click "more" button or when scrolling, show more records.

An example about this feature is when show commits in mercurial website "loading"
msg22029 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2015-07-29.15:56:04
I don't know what you are expecting but complaining about slowness with large data without pointing any bottleneck is pointless.
So I will be in favour of just making this issue as invalid.
msg22027 (view) Author: [hidden] (resteve) Date: 2015-07-29.15:36:03
When working with big data to show in tree view (not list view), is very slowly to show records when have hundred records. But when you have thousand records, finally you need to kill client because is impossible to show children records.

An example about tree view to show:

 > Product A
   > Subdivision 1
   > Subdivision 2
   > ...
 > Product B
   > Subdivision 1
   > Subdivision 3
 > Product C
   > Subdivision 4

If you are working with hundred records, when click arrow to display child records, it's ok, slowly but finally get childreen fields. But when you are working with a lot of records (in this example, 27964 products to display and each product have some subdivisions related each product) is impossible to show child.

Tested with different s SO (linux and windows) and different s laptops and desktops machines.
Date User Action Args
2018-03-09 19:14:31roundup-botsetmessages: + msg38916
2018-03-09 19:13:55roundup-botsetstatus: testing -> resolved
nosy: + roundup-bot
messages: + msg38915
2018-02-20 18:18:09cedlinkissue7151 superseder
2018-02-20 17:53:02reviewbotsetmessages: + msg38514
2018-02-20 17:52:46reviewbotsetnosy: + reviewbot
messages: + msg38513
2018-02-20 17:24:29cedsetpriority: wish -> feature
2018-02-20 17:24:25cedsetstatus: in-progress -> testing
reviews: 44641002,44021002
messages: + msg38510
keyword: + review
2018-02-20 16:43:22cedsetmessages: + msg38507
2018-02-20 15:50:34cedsetstatus: chatting -> in-progress
assignedto: ced
component: + sao
messages: + msg38501
type: feature request
2015-09-16 17:22:01restevesetmessages: + msg22392

Showing 10 items. Show all history (warning: this could be VERY long)