Skip to content

Minimum Specs for GSA Platform Identifier – Avoiding 100% CPU & Maximizing URL/min?

AnonymousAnonymous
in GSA Platform Identifier

Hey guys,

I’m running GSA Platform Identifier and hitting 100% CPU constantly. Even with good download speed, I struggle to keep a consistent ~10k URLs/min, while I’ve seen others reporting 40k+ URLs/min.

https://prnt.sc/_OtRCCSlO4JG

What I’d like to know is:

  • What are the minimum VPS/dedicated server specs to avoid CPU bottleneck (so it’s not stuck at 100%)?
  • Which resources matter most for higher throughput – more cores, higher clock speed, or RAM?
  • Any tips on tuning settings (threads, bandwidth limit, disk type) to push URL/min higher?

Basically, I’m trying to figure out the sweet spot for hardware so GSA PI can run at max speed without choking the CPU. If anyone has benchmarks or real-world numbers (e.g., what specs gave you 40k+ URLs/min), that would be super helpful.

Thanks in advance!



Comments

  • AnonymousAnonymous
    edited June 13

    This is my record so far sharing in case it helps others who struggle with CPU spikes in GSA Platform Identifier.

    I had to enable bandwidth limit and disable all other filters to stop the CPU from constantly hitting 100%. With this setup, the system now runs stable at around 60–70% CPU on average.

    I’ll continue experimenting with gradually raising the bandwidth limit to see how much the system can tolerate. For now, filters are not worth it they only consume CPU cycles and barely add 1% improvement, if at all.

    Additional tweaks that helped:

    • Save recognized links interval → set to 600 seconds (instead of the default 2). This reduces disk I/O and CPU overhead, giving more throughput.
    • Auto save projects → set to 60 minutes. Less frequent autosaves mean fewer interruptions and lower CPU usage.

    Tips for others:

    • Always keep CPU usage in the 70–85% range. That’s the sweet spot where you get maximum URL/min without choking the system.
    • Split huge datasets (e.g., 100M+ URLs) into smaller projects (10M–20M each). This balances load and increases URL/min.
    • Raise bandwidth limit step by step (e.g., 5120 → 8192 → 12288 kb/s) and monitor CPU. If it stays under 85%, you can push further.
    • Don’t max out threads immediately. Start with ~200 then adjust based on CPU stability.

    With my current setup (4 cores), I’m hitting around 13k links/min, and realistically this can scale up to ~20k links/min if tuned properly. That’s already solid performance for a 4‑core machine.

    However, if the goal is 30–40k links/min or more, you’ll need a higher‑spec server at least 8 dedicated cores (preferably 16) and more RAM (16–32 GB). That allows you to run 3000+ threads without pegging CPU at 100% constantly.

    With these settings, I’ve seen a clear jump in performance and stability. Hopefully this helps others squeeze more speed out of GSA PI without burning their CPU.

    https://prnt.sc/sb6Lw2w0WwFu

    https://prnt.sc/kcoq-JiNZfVi

    https://prnt.sc/ITd7IaizUqfh

    Thanked by 1organiccastle
Sign In or Register to comment.