-
Notifications
You must be signed in to change notification settings - Fork 233
Labels
module: RItype: enhancementImprovements that slightly enhance existing functionality and are fast to implementImprovements that slightly enhance existing functionality and are fast to implement
Milestone
Description
We started in #7707 to improve the time of getting the score and we had a meeting with @nicomollet and @piotrbak and we knew that the average time in SaaS to get the job done is 30 seconds more or less, but most of time is coming from the plugin.
So in the mentioned issue we fixed a good part of this issue by send the request directly to SaaS instead of waiting for the first cron to add the job into SaaS and get job_id.
Here we need to add more enhancement to make things faster, Let's discuss our options here:
- We can ask the @wp-media/engineering-wpr-addons-team to return the average queue processing time in seconds (this can be static number from their side but we need the control to be from SaaS so we can easily change this time based on needs) with the job_id and once we get this response we can directly create action scheduler single task to run after this average time, this will save us from waiting a minute to get the next CRON without affecting the normal workflow.
- We can check if we can create a dedicated queue runner for Rocket Insights feature to work every 30 seconds instead of 1 minute but I believe this will require code refactoring but we can check.
For me I like starting with option 1 as a start, what do u think?
Before starting in this issue, we need to get the numbers before to be enhanced with the selected approach and getting the numbers after.
Metadata
Metadata
Assignees
Labels
module: RItype: enhancementImprovements that slightly enhance existing functionality and are fast to implementImprovements that slightly enhance existing functionality and are fast to implement