What should you avoid when designing queries to prevent performance issues?

Keeping "batchSize" as -1 can lead to performance issues because it instructs the system to retrieve an unlimited number of records in a single query. This can put a significant strain on system resources, leading to memory overflow, increased processing time, and degraded performance, especially when dealing with large datasets. Setting a specific batchSize allows for better control over the number of records processed at one time, helping to optimize performance by reducing the load on the system and enhancing responsiveness.

Using primary keys as sort identifiers, for example, is generally a best practice when designing queries because primary keys are indexed, which makes sorting operations faster. Implementing filters effectively is essential as it ensures only relevant data is fetched, thereby improving the efficiency of queries. Utilizing nested queries can sometimes lead to complexities and performance bottlenecks, but when done correctly, they can also be a powerful way to organize and simplify data retrieval processes.