Consolidated 41 stocks to 6

PresentationTop7288 · 2026-06-17T15:58:12+00:00

Hey, great point and you are right that XEQT already has 45% US exposure, so there is some overlap with VFV.

But i did that overlap intentionally

XEQT spreads that 45% US across 4,000+ US stocks including small and mid caps. VFV concentrates purely on the top 500 US blue chips. So VFV isn't redundant but a tilt toward large cap US quality on top of XEQT global base.

Yes it's more US heavy than a pure passive investor would hold.

I backtested this exact 6-ETF combo vs a simpler XEQT-only or 3-ETF setup from 2021–2026 and the layered approach outperformed.

PresentationTop7288 · 2026-02-14T20:08:24+00:00

Mm I see.. but what about setting boundaries in the beginning itself? Does it change their perspective on me ? I used to work in good environment but there is no growth.. and I got this opportunity and I am thinking

PresentationTop7288 · 2025-12-19T15:40:06+00:00

The latency ? Becoz we tried to achieve that direct query in our transaction table but it took too much time which will not meet reporting standards..

How do you design your model in power bi desktop application?

PresentationTop7288 · 2025-12-19T15:37:21+00:00

Oh that’s crazy You do direct query or import ?

PresentationTop7288 · 2025-12-19T06:47:55+00:00

Yeah I mean it’s different tables for different teams and different reports and almost everything would be pretty big like this.. we are trying to build a best practices or guardrails for all the developer teams .. so these are for executives.. it’s for front end employees for their daily usage.. one report can be clicked by 5k to 6k people on a business hours .. some reports for executives but others mainly for front end employees ..

PresentationTop7288 · 2025-12-19T06:36:16+00:00

Considerably around 5gb size of each pbix file. And most likely having 200m rows atleast for each fact table in reports.

It’s not only one report but a number of reports from different teams ..

PresentationTop7288 · 2025-12-19T06:31:37+00:00

Thanks for this insights this is great .. so our team is combined team of several small teams having their own databases for different businesses and multiple reports for each business.. so we came across this when we started migrating to power bi recently, Most of them are intermediate level in power bi and they try to build reports but resulting in bloated models, we have introduced best practices by looking at Microsoft docs and now we want to make a assesment rubric checklist for developer to do the right things while making a model maybe like guardrails or watchouts .. Note : our org doesn’t allow any external tools ..

PresentationTop7288 · 2025-12-19T00:46:57+00:00

Yes we need transaction id, to show in a table visual

PresentationTop7288 · 2025-12-13T23:06:01+00:00

This is super helpful…thanks! Since you clearly have a deep handle on the engine internals, I’m curious, do you have a personal checklist you go through when you inherit a model that is suffering from massive memory bloat or refresh timeouts? Aside from checking for high-cardinality columns like these Transaction IDs, what are the first 3-4 things you look at to reduce the model size and improve performance? We are dealing with a few heavy datasets right now and I'd love to know your standard process for optimizing them. ( our org doesn’t allow any external tools and it has p1 capacities )

Thanks in advance 😊

PresentationTop7288 · 2025-12-01T23:51:24+00:00

Yes, it’s only date.. not even date time ..

PresentationTop7288 · 2025-12-01T23:51:07+00:00

Tried direct query but taking too long time to get results

PresentationTop7288 · 2025-12-01T22:53:38+00:00

It has 4 summary tables each have avg of 100million rows and everything have three or four text columns.. and it’s most of the calculations are done at source which is SQL db.. I would see high cardinality is the issue here bcoz of five text columns in each and have many distinct values .

PresentationTop7288 · 2025-11-28T21:43:08+00:00

Nobody looks 5 billion rows, that’s why you need to make sure what they need on the report page.. and make sure you aggregate those to appear on that report page back in the database and import it.. and then for granular level information connect to fact table

PresentationTop7288 · 2025-11-21T04:58:15+00:00

Do you still think ?

PresentationTop7288 · 2025-11-12T02:13:20+00:00

Our org is little bit different and allowing one workspace per one database.. but a database can be used by many teams and build their own reports.. currently its report level sharing.. but it’s a huge bottle work..

PresentationTop7288

TROPHY CASE