Le sam. 20 mai 2023 à 17:27, p····· g······· <pra...@gmail.com> a écrit :
> hi Romain! > 2.1.4 uses like 1-3% per instance. > 2.2 is maybe 1% more under normal usage BUT for the radio in question it > just grows up to using all available % of the core and catch-up messages in > log (not sure what happens first - cpu hog or time deficit). > the cpu is loaded around 10%, no big deal, it's not a tight virtual > machine filled server... > with latest 2.2 rolling build it just trips completely... but just this > one radio, the config you have. > Hmm. This sounds like a bad issue indeed. Any hint about what's going on? Does it loop on things? Or get stuck? > P > > > On 20 May 2023, at 19:58, Romain Beauxis <romain.beau...@gmail.com> > wrote: > > > > > > Yeah I have noticed some changes on that level. Essentially, it looks > like we are able to run do better parallel initialization of sources. On my > machine I can see more than one core being utilized during the initial > sources preparation, which is cool. > > > > I'm not sure yet what to do in your case. What's the total CPU load when > running on 2.1.4? It seems to me that the script is already on the edge of > the maximum CPU/memory capacity in 2.1.4 so any increase in CPU and/or > memory usage, being a bug like we just fixed or an "improvement" as I think > this is, ends up pushing it to the wrong side and choking. > > > >> > > > _______________________________________________ > Savonet-users mailing list > Savonet-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/savonet-users >
_______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
