This is a fairly large list to load into Yellowfin, though using cahced filters should speed this up.
However it may still need to load all the results from the YF database.
When a filter is cached, the values are loaded from the source database, converted to an xml document and stored in the Yellowfin database.
The results are also cached in memory for up to 24 hours, after 24 hours they are removed.
[i]This is to stop it from using up too much memory. /[i]
When a report uses a cached filter, it gets the results from the memory cache first if possible, and if not will load them from the xml document stored in the YF database (and add it to the memory cache).
When the cached filter is loaded from the YF database, it loads the XML document that includes the entire result set for all combinations of dependant filters (500000 values in your case).
Loading this document and converting it back to a native java object could take a while for a large data set like this, though it shouldn't do it every time the report is run, only once per day at the most.
So in saying this does your report take a while to open each time?
By 'open' we mean simply launching the report, and not running the report.