How can you optimize entity queries in OFBiz for large datasets?

Several framework-level levers help before reaching for custom SQL:

• Select only the fields you need with an EntityListIterator instead of full GenericValue objects when scanning large result sets.
• Use findList with an EntityCondition that maps to an indexed column, and confirm the matching index actually exists in the entity's entitymodel.xml index definitions.
• Paginate with the query's built-in offset/limit support, used automatically by list-type form widgets, rather than loading an entire table into memory.
• Turn on entity caching for reference-style data that's read far more than it's written.
• For genuinely complex reporting joins, define a view-entity once so the join is planned consistently instead of re-derived per call.

If none of that is enough, the Entity Engine still lets you drop to a custom finder or, as a last resort, a Java method issuing hand-tuned SQL through the same datasource - but that should stay the exception, not the default approach.