CPU Load Gen: High-frequency search burst script (10β1000 Hz)
Tooling: Custom Python benchmark with randomized query load
YaCy Peers:
agent-asx β running on RAID 5
agent-ramdrive β running on tmpfs RAM disk
Observations
agent-asx (RAID 5 backend)
CPU Usage: Peaks at 1600%
Response Times:
Min: 0.01 s
Max: 51.62 s (!)
Average: 0.82 s
Issues: Performance degraded under load, visible spikes in response time due to disk I/O bottlenecks (jbd2 activity + thread stalls)
agent-ramdrive (RAM-backed storage)
CPU Usage: Peaks at 909%
Response Times:
Min: 0.01 s
Max: 7.89 s
Average: 0.15 s
Result: Maintains low-latency searches even under extreme query pressure
Conclusion
Running YaCy on a RAM-backed temp store significantly improves query responsiveness and stability under high load. While RAID 5 can handle normal indexing workloads, it chokes under bursty traffic, introducing latency up to 50+ seconds.
RAM-backed deployments on high-memory systems like the DL360 G8 are ideal for:
I am curious why your CPU usage is so high. I have it running on an i9-10980xe box (18 core) and off of a RAID1 array hard drives, and I can completely saturate a 1Gbit/s internet link if I allow it to and yet only consume less than 10% CPU. Given that I can completely saturate a 1Gb/s link with it on a hard drive RAID array, I havenβt seen much incentive to wear out ssdβs fast.