I can make something "pretty" in Tableau faster. It takes a little more work to get some visuals looking less "MS Office" but there are tons of custom visual options and the ability to code your own. I use both Tableau and Power BI (and a bit of R, Big Query, Google Data Studio and whatever stack the client has) but over the years where there's been a choice I've leaned more into Power BI if the client doesn't have a preference. And if you've not looked in a while I'd suggest you look again - they do 10+ releases a year (basically once a month with a couple of breaks around holidays) and the featureset has grown massively, whilst the code/engine efficiency has improved immeasurably. I suspect if you're deep into Tableau only then you've not played with Power BI that much, and at first sight/first use its a very different approach and concept. Its a little slower and lacks some niceties and helper apps like Tabular Editor, but for thin reports built on existing data models authored in desktop its perfectly viable In Service you can build data flows, datasets and reports in the web browser. And just for funsies some queries do both - call back to source for query folding AND then hold that in RAM to run the live calcs.Īnd that is all for authoring in Desktop. Oversimplifying it, Power BI processes in two ways - at import/on open which is Power Query and uses (mainly) CPU, then the formula engine for measures which mostly works in RAM - which is super quick but can eat through RAM. 16GB of RAM is likely to be the limiting factor. You can totally use Parallels - I have clients on Macs and Power BI workbooks I build them on Parallels with no issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |