Hello helpful meteor experts :wave: we are having issues tracing down some reactivity problems after updating to meteor 3.0.3 . We did all the async migrations already on the last stable build still running meteor 2.10.0. The 3.0.3 build just updated meteor, all the packages and the node version. B…

I have no production deployment yet but am starting at 3.0.4 - rapid prototyping mission critical system migrations. I will take your case to heart and try to reproduce at mid-scale while I have the old system still running in parallel to compare and see if anything gets missed. ( Mirroring redundan…

Sure, most interesting is probably, anything closely related to meteor core logic: ▶ Mongo 6.0.18 ▶ Meteor versions ▶ Full build script React 18.3.1 Default build tool Happy to provide more details if there is anything else of interest?

@kfritsch , is there any chance that you are stress-loading this instance? Or this might be happening when the system is lacking resources? There was a pending issue posted by the core team related to performance wherein under stress, Meteor 3 missed some updates compared to the same app running in …

I doubt that the app servers were stressed at that time, at least not when it comes to cpu or memory (The spike to 100% was after we were back on meteor 2). Is there another metric I should check there? ▶ App server cpu and mem When I look more carefully at the mongo metrics then yes, the mongo prim…

@kfritsch , check this topic [image] Meteor 3 Performance: Wins, Challenges and the Path Forward announce Motivation After the Meteor 3 launch, we planned our next steps, our roadmap is public . Before introducing new features or packages to the framework, we wi…

Another metric to watch for is event loop latency, as you might not need the CPU at full load for Node.js to experience performance issues. Once the event loop starts to lag, things slow to a crawl or get out of sync. It seems to happen in high-load scenarios due to garbage collection, a huge numbe…

We were not aware of the whole node event loop latency topic. We will have to add that to our tracing, thanks for pointing that out. We will also follow the meteor 3 performance ticket, but I think there is actually quite a bit we can do on our side to reduce our resource usage. Will give an update …

Alongside the specific question, wondering if any Meteor ninjas or historians can recall if there are other measures being taken in the wild, with or without performance refactoring done first. Not expecting to keep old/bad/lesser practices under the hood, but treating those like a simulation of fut…

This looks familiar to what @radekmie is going for with DDP Router: [image] Introduction of DDP Router announce Intro I’ve been thinking about Meteor performance a lot recently and I have one crazy idea… Would any of you be up for a talk about it? I can write…

Thanks very much for the detailed comments @leonardoventurini . Glad I am going down a known path but one less traveled, which might be an edge of Meteor … I would fan to flame your crazy side. I am encouraged that you are brave and open minded, it seems. And I see but dismiss burn-in from the curre…

Reactivity problems after migrating to meteor 3.0.3

help

digitalextremist October 29, 2024, 3:29am 12

Moved out of the way of this thread ( too late ) when I almost came back just to park my bike in the shed less slovenly, and caveat “smoke signal” comment. Expanded to the actual point here: