Re: Improving Message Forwarding Processor Deactivate Implementation
Thanks for the response Isuru. I will work on the improvement. On Sun, Dec 6, 2020 at 6:18 AM Isuru Udana wrote: > Hi Shafreen, > > On Wed, 2 Dec 2020, 22:00 Shafreen, wrote: > >> Hi All, >> >> At the moment when we deactivate the Message Forwarding Processor (MFP) >> what happens internally is that the scheduler keeps on executing the MFP >> according to the given interval. Inside the MFP we just have an if >> condition to check whether the MFP is deactivated. If so, it will >> immediately skip the execution of MFP. >> >> IMO, this redundant execution of MFP wastes CPU cycles. This could be >> especially problematic, when running in a constrained environment where the >> CPU cycles are limited. We can improve the implementation by deactivating >> the scheduler job itself and reactivating when needed. >> >> WDYT ? >> > +1. That should be the correct solution. > >> >> Thanks, >> Shafreen >> >
Re: Improving Message Forwarding Processor Deactivate Implementation
Hi Shafreen, On Wed, 2 Dec 2020, 22:00 Shafreen, wrote: > Hi All, > > At the moment when we deactivate the Message Forwarding Processor (MFP) > what happens internally is that the scheduler keeps on executing the MFP > according to the given interval. Inside the MFP we just have an if > condition to check whether the MFP is deactivated. If so, it will > immediately skip the execution of MFP. > > IMO, this redundant execution of MFP wastes CPU cycles. This could be > especially problematic, when running in a constrained environment where the > CPU cycles are limited. We can improve the implementation by deactivating > the scheduler job itself and reactivating when needed. > > WDYT ? > +1. That should be the correct solution. > > Thanks, > Shafreen >
Improving Message Forwarding Processor Deactivate Implementation
Hi All, At the moment when we deactivate the Message Forwarding Processor (MFP) what happens internally is that the scheduler keeps on executing the MFP according to the given interval. Inside the MFP we just have an if condition to check whether the MFP is deactivated. If so, it will immediately skip the execution of MFP. IMO, this redundant execution of MFP wastes CPU cycles. This could be especially problematic, when running in a constrained environment where the CPU cycles are limited. We can improve the implementation by deactivating the scheduler job itself and reactivating when needed. WDYT ? Thanks, Shafreen
