Skip to Content (Press Enter)
UserImage.jpg
Pedro Custódio
8Views
1Comments
[Feature Toggle Library] High CPU spikes every 30m caused by Timer_FeatureToggleHits_Sync
Question
Forge
OutSystems 11
Service
feature-toggle-library
Service icon
Feature Toggle Library (O11)
Forge asset by Experts
Application Type
Service

Hi,

We detected severe linear CPU degradation in a Production environment. The issue is triggered by Timer_FeatureToggleHits_Sync (from FeatureToggleManagement_CS), which is scheduled to run every 30 minutes.

It seems that as the production log tables grow, this synchronization query is becoming increasingly heavy, causing considerable database overhead during its execution. During off-business hours, when the environment is otherwise idle, this 30-minute sync process alone is driving CPU utilization up to 30%~40%.

Since these hits appear to be used only for LifeTime metrics, we plan to disable this timer. We also noticed the latest April version allows disabling log generation entirely.

Does this timer serve any other critical application purpose we should be aware of before turning it off? We are planning to disable it and upgrade the component to disallow the logs.

Thanks!

0
0
13 days ago
Copy Link
2023-12-26 10-35-28
OutSystems Neo
Staff
AI Generated

You can safely turn that timer off.

Timer_FeatureToggleHits_Sync (from FeatureToggleManagement_CS) is only used to move feature‑toggle hit information from the application logs into the Feature Toggle/LifeTime side so you can see usage/analytics for toggles. It doesn’t participate in the actual evaluation of feature flags at runtime.

In other words:

  • Disabling the timer:
    • Stops the periodic sync of “hits” from logs.
    • Prevents those hits from appearing in metrics/analytics (e.g. in LifeTime/FeatureToggle dashboards).
    • Does not affect whether a toggle is ON/OFF or how your applications read and apply the toggles.

Given that:

  • You are not relying on those metrics for operational decisions, and
  • You are facing measurable CPU and DB overhead as logs grow,

your approach is sound:

  1. Disable Timer_FeatureToggleHits_Sync in Service Center (or via the timer‑control logic if you prefer). Setting the next run to a far future date effectively disables it while mimicking “Deactivated” behavior in Service Center.Enable-Disable Timer Having Schedule?
  2. Upgrade to the latest April version of the component and enable the setting to stop generating those hits/logs altogether, so you don’t keep accumulating unnecessary data.

The only downside is loss of feature‑toggle usage stats. If no one is consuming those, there’s no functional risk to your apps.

0
0
12 days ago
Copy Link
This answer was AI-generated. Please read it carefully and use the forums for clarifications
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.