The Pound man page says "with a lot of simultaneous requests it will use quite a bit of CPU and memory." This is a relative statement and does not give any guidance as to the order of magnitude of memory required. Some examples would be helpful:
  • 1 request per second for a single proxied service: ~xxx KB/MB RAM
  • 10 requests per second: ~xxx KB/MB RAM
  • 100 requests per second: ~xxx KB/MB RAM
  • 1000 requests per second: ~xxx KB/MB RAM
  • Is there a linear relationship between requests/second and memory required?

Presumably the load imposed by Pound varies according to the work it has to do. Requests using http on port 80 that are redirected to https would presumably not require much CPU because SSL/TLS is not involved. OTOH, I expect it would require more computation to redirect an https request from port 443 to another port, and the amount of computation would be comparable to that required by the webapp itself when decoding the packet.

Thanks,
Mike

-- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.

Reply via email to