Hello,
We are experiencing a different refresh time for the datasets. If we use the new “dataset type” it takes 3 minutes, the same view/materializedview loaded with the “old dataset type” takes 14 second…..
Hi @remba87 ,
Are both datasets configured identically? Something to note with the new data prep experience is that while it does offer features that were not available in the old data prep experience, there have been some community posts that mention there are some limitations in the new data prep experience. The new data prep experience is still a relatively new and from what I understand is something that the Quick Team is actively working on. Since you know the refresh time is considerably better within the old data prep experience, I would recommend continuing to use that since the old data prep experience is still available.
Additionally, I would also recommend you check out this resource that fuller talks about features that are so far not supported in the new data prep experience (Features not supported in the new data preparation experience - Amazon Quick).
Hello,
yes the datasets are identical 
thank you for the information!
1 Like
Hi @remba87,
If the datasets are identical then I would say the refresh rate is due to which data prep experience you use. Like I previously stated, since you know your dataset works better with the old data prep experience, then I would continue using that moving forward over the new data prep experience.
If you still have any additional questions related to your initial post, feel free to share them.
Thank you
Hi @remba87
It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.
If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.
Thank you!
Hello, yest the datasets are identical and we are not doing any PP do the dataset, so I do not understand the difference in time refreshing it
Hi @remba87,
My assumptions are that as the new data prep experience is still in a bit of a development stage (signaled by the number of features that are currently still not yet available), is that something additional is happening behind the scenes that leads to the variance in refresh time. If speed is of utmost importance to your scenario, I would suggest continuing along with the legacy version until they’ve rolled out feature updates and a more solidified final product for the new experience.
Hi @remba87,
Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.
Thank you
Hi @remba87,
Since I haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.
Thank you