It can take up to half a day to explode a modest-sized nested collection (0.5m).
On a recent Xeon processors.
See attached pyspark script that reproduces this problem.
This script generate a number of tables, with the same total number of records across all nested collection (see `scaling` variable in loops). `scaling` variable scales up how many nested elements in each record, but by the same factor scales down number of records in the table. So total number of records stays the same.
Time grows exponentially (notice log-10 vertical axis scale):
At scaling of 50,000 (see attached pyspark script), it took 7 hours to explode the nested collections (!) of 8k records.
After 1000 elements in nested collection, time grows exponentially.