Tabular Model Partitioning to help Developers

Developing Tabular models in Visual studio can be super painful as the interface gets very "sluggish" as tables get larger. in some cases customers have told me they wait 5-10 minutes a go to say change the name of a column or add a calculation Another of the annoying things about tabular models is that if you have a partitioned fact it can be only processed on one thread PER TABLE. If we start processing and profile queries to SQL Server we will only see one of them, rather than one per partition or one per core as you get with MOLAP. There is pretty much no way around this ;-(