[Performance issue]: NEP is taking more than 31 minutes to write the data for single device into DB.

[Ziabatcha]

Started NEP in preprod, sliding window as 250, sync period as 8 hrs. But only ~2500 devices are stored into DB which took ~6.5 hours.

Snippet:

[appserver@mwappserver2 ~]$ docker logs --since=24h netexplorerproxy_v1.1.0a_impl 2>&1 | grep -i "Dat
[11:31:07.898] INFO (1): Data fetching starts 8/13/2025, 11:31:07 AM
[19:31:07.902] INFO (1): Data fetching starts 8/13/2025, 7:31:07 PM
[03:31:07.901] INFO (1): Data fetching starts 8/14/2025, 3:31:07 AM
[appserver@mwappserver2 ~]$ date
Thu Aug 14 09:50:36 CEST 2025

curl -X POST "http://x.x.x.x:xxxx/v1/provide-list-of-devices-in-nep" -H "accept: application/json" -H "Authorization: ---------------------------" >& test1.txt
cat test1.txt | grep "mount-name" | wc -l
2337

[jain-siae]

Hi @Ziabatcha ,

Can you please share the complete logs ,so that we can check that the issue.

Just a curiosity , how are we deducing that for a single device software is taking 31 minutes?

From Ticket : Started NEP in preprod, sliding window as 250, sync period as 8 hrs. But only ~2500 devices are stored into DB which took ~6.5 hours.

If 2500 devices data is stored in 6.5 hours , this is about ~6 min per device.

Please let us know if we are missing something

Thanks,
Harshit

[latta-siae]

Testing team is keep under control the issue.
It will be closed after pre-prod tests

[Ziabatcha]

Tested in v1.1.0.d_impl. This issue is not seen.
But the sliding window is 3 because of issue #247

we will retest once the sliding window issue is solved.

[kmohr-soprasteria]

@Ziabatcha and @latta-siae:
is this issue resolved with the previous or current release?

[latta-siae]

This issue seems no longer observed.
Waiting feedback from validation team