P3-Core-Dev-Team / P3-Q-A

This repo is for tracking features
Other
1 stars 0 forks source link

ADS-Background Search- Background Search-Taking Longer Time - ABB #177

Closed AshsubM closed 19 hours ago

AshsubM commented 5 days ago

Describe the bug The Background Search is taking longer time than usual.

image

Before Deployment it hasn't took this much time for the seaches , but now it is taking longer time

Build no :2024.09.45542_P5 Region : https://dev.ads-platform3.elis.abb.com/login Client : ABB

ClementJosh21 commented 5 days ago

@AshsubM Can you give me some info about the data involved in the BG search?

AshsubM commented 5 days ago

@ClementJosh21 This is a CRT search, it fetch around 1494958 records from the TABLE name INDEX. The total number of records in the INDEX tables is 15028389

ClementJosh21 commented 5 days ago

@AshsubM Records seems to be huge. Job got completed or you are still facing the same issue?

AshsubM commented 5 days ago

The jobs are completing sequentially. The first job took 14 minutes to complete, and only after that the second job get triggered, and completed in 4 minutes.

Sethu-P3 commented 4 days ago

We have taken the time stats report for all searches .It didnt went to background search. Totally we have 5 different searches and here attached the time stats report for these searches. ABB TIME Stats - Sheet-finall.pdf

dinesh-p3 commented 3 days ago

@AshsubM has confirmed that the search performed before the deployment was configured with limit of 10000, and now the configuration was changed to no limit and the record count was around 1 crore, As a result, the time taken to process the search is expected and is working as intended

AshsubM commented 3 days ago

Yes, Before the deployment, the Search limit Configuration was set to Custom Limit of 10000, and the stats for the each search results were taken with that limit configuration. So post deployement when we performed the search we found there were some time differences, then we checked the Search Limit Configuration was updated to No limit, and that's the reason for this time difference. Will check with the team and provide the update.

Our team member has changed the configuration limit from 10000 to No Limit, thats the reason it took background search.

Hence closing this issue