new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

OWASP Cheat Sheets · all subjects

application_security/performance

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Monitor event loop with toobusy-js to prevent DoS

Use the `toobusy-js` module to monitor event loop response times under heavy traffic. When response time exceeds a threshold, return HTTP 503 "Server Too Busy" to stop processing incoming requests and maintain application responsiveness. This prevents Denial of Service conditions.

Limit simultaneous open files, network connections and processes

Limit the number of simultaneous open files, network connections and started processes.

Optimize configuration for maximum message throughput

Configuration should be optimized for maximum message throughput to avoid running into DoS-like situations.

Limit CPU cycles for web service

Limit the amount of CPU cycles the web service can use based on expected service rate, in order to have a stable system.

Limit memory usage for web service

Limit the amount of memory the web service can use to avoid system running out of memory. In some cases the host system may start killing processes to free up memory.

Give your agent this brain