Replies: 2 comments
-
As far as resource usage, since ferox uses async/await, they're not full-blown OS threads (more can be read here). From a user perspective, you can easily set the default you prefer via ferox-config.toml. You can set the default at a number of 'levels':
If you wanted, you could tone it down for Target-A and have it cranked up for Target-B, etc... The actual reasoning behind why I chose 50? 🤷 It's roughly in line with similar tools and some value needed to be chosen. Is 10 or 15 a better option? Perhaps. But we could easily be having the same conversation about 10 or 15. An arbitrary default needed to be there, and it was designed to be very configurable in the event that the default doesn't suit a user's preferences. |
Beta Was this translation helpful? Give feedback.
-
I would highly recommend moving this to a much lower default... 50 threads could potentially take out a web server that maybe doesn't have the resources pretty quickly. In all of my testing, I try limit stuff to 10-15 threads by default, and then ramp up if the system looks to be stable. |
Beta Was this translation helpful? Give feedback.
-
Using 50 threads seems rather high as a default. Wouldn't it be better to have a default of like 10 or 15 threads as a default?
Beta Was this translation helpful? Give feedback.
All reactions