Forum Discussion
StreamBeforeRequestCompletes - Guidance for Mashup Container
You can change the container size per query in the PBI Desktop settings.
The "Stream" setting does seem to speed things up by not spooling everything. But all data that goes to the PowerBIgateway goes through the gateway. I don't the machine on which you have the gateway installed, but just because source to Local PowerBI is fast does not mean that the Gateway is going to be just as fast. Depends on the machine, is it working on other stuff, does it have enough RAM, processor power, etc. You said that you are worried about affecting all of the other reports, which suggests that yours isn't the only report potentially refreshing through the Gateway.
--Nate
Anonymous Thanks for the reply.
I wasn't clear in my question, but I was discussing the on-prem enterprise gateway, not the behavior of the PBI desktop.
>> The "Stream" setting does seem to speed things up by not spooling everything
Are there negative consequences? Do you use it by default on all your gateways? If I ask our server team to make this config change, then how will I explain the comment in there that says "do not change"?
>>You can change the container size per query in the PBI Desktop settings
Yes, it affects the desktop but I don't think this affects the behavior in the enterprise gateways. That said it might be nice if there was a way to influence the container sizes on the gateways. (on a report-by-report basis)
>> does not mean that the Gateway is going to be just as fast.
Right, the gateway "mashup container" seems to do nothing but slow me down. It runs as a .Net single-threaded CLR host. It restricts itself on RAM, and spends a massive amount of time on unnecessary I/O. For this particular case (a 1 GB fact table) I just wish the mashup container would "get out of the way" and let the data straight thru. I suspect I would save a little over an hour if it wasn't for the unnecessary caching and spooling to disk.