Forum Discussion
General dissatisfaction and performance issues
daaaaaaamn daniele.
Without knowing more, it's hard to say what's going on here, but I would be hesistant to quickly blame Power BI. I have clients using postgresql and have not heard these complaints.
Could be you have some crazy expensive calculated column (which gets recomputed during refresh)
Could be your are pull from postgresql via a view that performs badly
Could be your database hardware is failing
I'm pretty skeptical to make the blanket statement "Power BI performs badly against postgresql". It's *possible*, but... I'm skeptical.
Thanks for the reply Anonymous. I based my answer on what Greg_Deckler said, as i see he's very experienced and answers pretty much every topic here.
If you get "You should change database as an answer" from an experienced member, you would think he knows what he's talking about (and i think so).
Greg_Deckler not sure we are talking about the same service here. I've started the same free trial with 200$ credits free, and was about to start an SQL server. The prompted prices were not lower than 150$ per month. I might have done / selected something wrong maybe?
About the crazy calculations. Here's an example of a dashboard that fails to update:
4 tables with 680k rows of which 2 has 20 columns, one 17 columns and one 9 columns. Then other small tables with 30k records or 300 records.
There's one main key column in one of the big tables, where the other tables are in a 2 way relationship with, and yes there are a few calculations done, also in the big tables, but it's stuff like:
MyCalculation = CALCULATE ( COUNTROWS ( 'thistable' ), 'thistable'[thiscolumn] = "lorem ipsum" ).
I don't know if this is too much.
all of the data is fetched via connection string to an amazon server.
Anyway, the main issue is that online there's no way it's working, and on the desktop app, i need to refresh a minimum of 3 times, up to 10/12 to avoid getting errors like these 2:
-exception while reading from stream postgres
-error remaining connection slots are reserved for non replication superuser connections
Of which the second very seldom compared to the first.
And all of this happens even with really small amount of data from our PostgreSQL datawarehouse.
As i said, i really like Power BI and if someone could help solving this i would be a happy and thankful guy.
It sounds like you are spinning up an Azure SQL Server via Infrastructure as a Service (IaaS). What I am suggesting is that you spin up an Azure SQL DB instance instead. This is more of SQL Server database as a Service so more SaaS based. Much less expensive than running a server in the cloud.
I didn't realize that you were running your PostgreSQL box in Amazon. There could definitely be latency issues there going from on-premises to the the Amazon cloud or from Azure to Amazon. The nice thing about Power BI and using Azure SQL DB is that you can potentially have all of it in essentially one data center or at least all within Azure with fast connections between Azure data centers.
Listening to Greg_Deckler is indeed a good plan!
I just looked -- and have a client w/ an S1 instance in Azure ($30/mo), with 23 million rows of data using only 5gb of 250gb available... and I suck them all into power bi w/ no probs.
