Performance degradation of the boundary desktop upper than 2.0.1

Hi @dmitryroshchin

Thanks for the info.
We understand and to narrow this down more we just need some more numbers to see the difference. In one terminal can you run boundary cache status in order to retrieve the AuthToken Id and then run:
time curl -X GET --unix-socket /Users/roshin/.boundary/socket/daemon.sock "http://internal.boundary.local/v1/search?resource=targets&force_refresh=true&auth_token_id=<TOKEN_ID>" > /dev/null

Please repeat a couple of times and send us screenshots of the output.

In a separate terminal, please run the desktop client with logging enabled using BOUNDARY_DESKTOP_LOG_LEVEL=debug ./Boundary.app/Contents/MacOS/Boundary, and the logs are located at ~/Library/Logs/Boundary/desktop-client.log. Please search targets a couple of times and send us the logs of that as well.