I am conducting performance testing to measure the response time of suppliers’ results for a flight search application using Selenium with Java and TestNG. I have utilized invocation count and thread pool size settings. However, I occasionally encounter stale element reference exceptions. When this issue arises, it persists for around half an hour. Conversely, when it functions correctly, there are no problems for approximately 15 to 20 minutes before the issue recurs.

I have tried nearly every method available online to avoid stale element reference exceptions, including refreshing the page, using try-catch blocks and re-searching for the element after catching the exception, and employing explicit wait mechanisms. Unfortunately, none of these solutions have resolved the issue.
I have never used selenium for performance testing and have only one year of experience in
selenium as well.

solution to avoid the problem I am facing