# Quality Report Timing **URL:** \ **Category:** Evaluation and Benchmarking\ **Tags:** quality, performance, reports\ **Created:** [June 10, 2024, 4:14pm UTC](https://forum.datacebo.com/t/quality-report-timing/208 "2024-06-10T16:14:14Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pranav.rupireddy](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@pranav.rupireddy](https://forum.datacebo.com/u/pranav.rupireddy)\ **Post date:** [June 10, 2024, 4:14pm UTC](https://forum.datacebo.com/t/quality-report-timing/208/1 "2024-06-10T16:14:14Z")
I am noticing that the quality report takes a very long time (upwards of multiple days) - I was wondering if you had any suggestions to speed this up or if this could be improved? ---
**Author:** ![neha](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.datacebo.com/neha/32/15_2.png) [@neha](https://forum.datacebo.com/u/neha)\ **Post date:** [June 10, 2024, 7:01pm UTC](https://forum.datacebo.com/t/quality-report-timing/208/2 "2024-06-10T19:01:37Z")
Hi @pranav.rupireddy, I’m sorry to hear that. Are you running the report on a multi-table datasets? And would you mind providing more info about the dataset size for both real and synthetic – for eg. how many MB (or GB) is the full dataset, and how many rows/columns does it contain in each table? As a reference, our analysis shows that for a single table of data (around 98MB each for real and synthetic), it is taking around 10 min to generate a quality report. So I am wondering if you are trying this on a much large dataset, or one that has more complexity in terms of multi-table schemas? I can dig in further based on your responses. ---
**Author:** ![pranav.rupireddy](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@pranav.rupireddy](https://forum.datacebo.com/u/pranav.rupireddy)\ **Post date:** [June 11, 2024, 4:03pm UTC](https://forum.datacebo.com/t/quality-report-timing/208/3 "2024-06-11T16:03:07Z")
It’s multi-table. Table 1: Dimensions - 1000000 rows, 15 columns Real - 69206 KB Synthetic - 76018 KB Table 2: Dimensions - 23064914 rows, 91 columns Real - ~5 GB Synthetic - ~6 GB Table 3: Dimensions - 8142945 rows , 22 columns Real - ~1 GB Synthetic - ~1 GB ---
**Author:** ![pranav.rupireddy](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@pranav.rupireddy](https://forum.datacebo.com/u/pranav.rupireddy)\ **Post date:** [June 11, 2024, 4:06pm UTC](https://forum.datacebo.com/t/quality-report-timing/208/4 "2024-06-11T16:06:25Z")
Also, manually specifying the ID columns with the sdtype of id in the metadata has helped speed things up, though it still will likely take a day or two or more it appears ---
**Author:** ![neha](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.datacebo.com/neha/32/15_2.png) [@neha](https://forum.datacebo.com/u/neha)\ **Post date:** [June 11, 2024, 9:47pm UTC](https://forum.datacebo.com/t/quality-report-timing/208/5 "2024-06-11T21:47:48Z")
Hi @pranav.rupireddy thanks for the details. > manually specifying the ID columns with the sdtype of id in the metadata has helped speed things up 1. Got it. The quality report will comprehensively compute marginals and correlations for any statistical column (eg. numerical, datetime, categorical). Other concepts such as IDs, or PII values should not be marked with these sdtypes. Perhaps it is best to go do another sweep of your metadata to double-check this? If a column is accidentally marked as categorical and has _extremely high cardinality_ (aka a large number of different values), that may cause an issue. So be sure to especially check for this. 2. Additionally, your dataset size seems to be quite high. To get you unblocked ASAP, you can try to subset the multi-table data (real and synthetic) using the [**get\_random\_subset**](https://docs.sdv.dev/sdv/multi-table-data/data-preparation/cleaning-your-data#get_random_subset) function. Then try running the quality report on the subsetted data – if you repeat this process a few times, it will become a good approximate value. In the meantime, I will file and track a new feature request for improving the performance of the Quality report natively.