Re: [PATCH] Redirect on Error

There is no proposed patch to affect all these changes. There are fine ways to print errors that don't necessitate having them loaded at run time. They could be in a dbm file, or even a flat file hierarchy and loaded on demand. This would not be as fast as a hash table, but when you're actually printing errors, a slight overhead seems acceptable (to me, ymmv) On Monday, November 25, 2002, at 10:27 PM, Ilia A. wrote:

On November 25, 2002 09:59 pm, George Schlossnagle wrote:

By the way, could you please advise by how much I will need to increase the power of my server(s) to maintain the same level of performance?

Why would this need to kill your performance if you're not throwing errors?

Because errors need to be loaded into memory by some mechanism, stored in a hash table? Meaning that during startup I will be penalized for this process. Hash table has it own overhead as well meaning that PHP memory usage will increase, for a server running 200-300 apache children constantly even a small increase will count. This will also make PHP shell scripting impractical due to the high start costs of a PHP binary. Ilia