3 ms·
>How much time does nginx spend parsing HTTP requests compared to waiting for network or disk IO? Enough that they choose to use much more obtuse code? Not to
by MichaelGG 13y ago
>How much time does nginx spend parsing HTTP requests compared to waiting for network or disk IO?
Enough that they choose to use much more obtuse code? Not to mention network/IO scale independently so it's not a relevant comparison. I wrote a packet capture system that spent about 70% of its capture/index CPU budget on parsing.
A torture test is only clever if it's not absurd because of a thousand edge cases. Then it just reflects the stupidity in the protocol design.
Do you have any possible use of terrible parsing rules that encourage security holes? HTTP is commonly used outside browsers because it's a simple wrapper for a TCP-RPC model. Request something, get a response. And none of the features depend on the stupid parsing rules - absolutely no one and nothing benefits from that. Except perhaps contractors billing hourly.
- rbanffy 13y ago> Enough that they choose to use much more obtuse code? They certainly had it profiled before they optimized it. There must be some numbers somewhere. "Enough" is hardly an acceptable answer.