You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Jacques Le Roux (Jira)" <ji...@apache.org> on 2022/10/01 17:14:00 UTC

[jira] [Comment Edited] (OFBIZ-12694) Screen partymgr/control/findparty is taking long time to load parties

    [ https://issues.apache.org/jira/browse/OFBIZ-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607772#comment-17607772 ] 

Jacques Le Roux edited comment on OFBIZ-12694 at 10/1/22 5:13 PM:
------------------------------------------------------------------

I made another test with trunk HEAD. Using a clear-cache request for 200 users each time I get locally as a whole:
* no change:  around 20 sec
* removing only ClassificationGroup: 12 sec
* removing only ClassificationGroup and userLoginId: 7,5 sec
So yes it makes a difference

OOTB none of the ClassificationGroup is present so I guess we could remove it. For userLoginId it's a bit more annoying. Because if you want several at once it's convenient. I though tend to agree that it does not make much sense to want several of them at once.

I'd be OK to remove these columns but I'm not alone to decide. Some may think otherwise for reasons I don't know. So we need to check with the community. I can do that for you, let's see



was (Author: jacques.le.roux):
I made another test with trunk HEAD. Using a clear-cache request for 200 users each time I get locally as a whole:
* no change:  around 20 sec
* removing only ClassificationGroup: 12 sec
* removing only ClassificationGroupand and userLoginId: 7,5 sec
So yes it makes a difference

OOTB none of the ClassificationGroupand is present so I guess we could remove it. For userLoginId it's a bit more annoying. Because if you want several at once it's convenient. I though tend to agree that it does not make much sense to want several of them at once.

I'd be OK to remove these columns but I'm not alone to decide. Some may think otherwise for reasons I don't know. So we need to check with the community. I can do that for you, let's see


> Screen partymgr/control/findparty is taking long time to load parties
> ---------------------------------------------------------------------
>
>                 Key: OFBIZ-12694
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12694
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: party
>    Affects Versions: 18.12.06
>            Reporter: Balaji Yendamuri
>            Assignee: Jacques Le Roux
>            Priority: Major
>         Attachments: Image 003.png, image-2022-09-15-23-28-12-589.png, image-2022-09-15-23-30-53-379.png, image-2022-09-17-20-54-14-905.png, image-2022-09-19-23-51-30-225.png, image-2022-09-19-23-53-02-064.png
>
>
> findParty screen is having performance issue in latest ofbiz version
> findParty screen in latest 18 version is taking 30 sec to load 200 parties
> !image-2022-09-15-23-28-12-589.png!
>  
> But 
> findParty screen in 15.12 version is loading fast (no performance issue)
> My observation : 
> row actions is effecting lot in performance wise 
> I removed row actions and tested below is the load time 
> !image-2022-09-15-23-30-53-379.png!
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)