I tried this (using open and curl) and performance took too big a hit. The cpu was doing about 15% user and 85% system and I could only get about 40 req/s - I need to be around 70 to 100, which I am able to do when running many disconnected non-threaded scripts.
Starting up a process for each request unfortunately is too expensive, thank you for the suggestion, though.
In reply to Re^4: Threads and HTTPS Segfault
by onelesd
in thread Threads and HTTPS Segfault
by onelesd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |