Saturday, August 04, 2012 6:15 PM
Does Casablanca has a strategy regarding the possibility of the library/networking subsystem(which is WinHttp as I know of) to keep up with a large number of outstanding requests in case o stress testing ?
I have observed that without limiting in some way the number of requests made at some point to winhttp you can quickly get in high memory usage on winhttp.dll side and if you keep up adding requests (many of them failing in the end) you get out of control of your application memory.
Monday, August 06, 2012 2:30 PMOwner
No, but it's good to know that this is something you would like to see.
It would be hard to throttle overall system traffic, since we only have knowledge of one process at a time (Casablanca is entirely user-mode), but if that (single-process throttling) is what you are looking for, we can take a look at how it could be designed.
- Marked As Answer by raiderG Wednesday, September 26, 2012 8:28 AM
Monday, August 06, 2012 3:59 PM
Basically, what I end up implementing when using winhttp on my app is to throttle number of concurrent outstanding requests otherwise I end up with memory issues, eventually application being shutdown because of that (plus performance etc.) Yes, it's a per process limitation.
- Edited by raiderG Monday, August 06, 2012 3:59 PM