Why is Our Keyword Density Tool Struggling with Large Text Inputs for Content Optimization?

Hey everyone,

We run a pretty popular "Keyword Density & Frequency Checker" tool on AdsVolt.com, and it's been super helpful for a lot of folks working on their SEO and content strategies. Recently, though, we've hit a snag. Both our users and our internal monitoring have been reporting significant performance degradation, especially when they try to process really long articles or large blocks of text. It seems to struggle most after we tried to implement some new features aimed at improving overall content optimization capabilities.

The observed behavior is pretty frustrating for everyone involved: the tool either takes an incredibly long time to return results, or in some cases, it completely times out, leaving users hanging. We've started seeing increased CPU usage during these heavy operations, and our logs are sometimes spitting out errors like this:

[ERROR] 2023-10-27 14:35:01 ProcessingTimeout: Keyword analysis for 15000+ words exceeded 60s limit.
[WARN] 2023-10-27 14:35:05 High CPU usage detected on /api/check-density endpoint.

We've already looked into basic server scaling and some initial query optimizations, but it really feels like the core text processing algorithm for calculating keyword density is the main bottleneck here. Has anyone faced similar issues with text analysis tools? Any tips on optimizing these kinds of algorithms for handling large inputs more efficiently, or perhaps specific server configurations that could help prevent these timeouts without completely re-architecting everything?

Help a brother out please...