OK, I can't by inspection or by test see any performance differences between the 2 implementations (in fact, the older one, in some benchmarks, was slower due to the string operations in the critical path)... Any ideas? On Nov 26, 2013, at 4:23 PM, Jim Jagielski j...@jagunet.com wrote: Thx...
On 02.12.2013 13:18, j...@apache.org wrote: Author: jim Date: Mon Dec 2 12:18:19 2013 New Revision: 1546976 URL: http://svn.apache.org/r1546976 Log: Merge r1544820 from trunk: mod_lua: Fix compiler warning by using correct APR_SIZE_T_FMT and APR_OFF_T_FMT format macro in debug
Hi, one of my thought was the change from worker-s-name to ap_proxy_worker_name(r-pool, worker) in logging function. ap_proxy_worker_name allocates memory in the pool and performs some operations on strings (apr_pstrcat). These operations are performed in all cases, even if
But from what I see, all of those are during non critical paths. It's like when workers are being defined, initialized, etc and that's only done during config or when added via balancer-manager. On Dec 2, 2013, at 8:09 AM, Marion et Christophe JAILLET christophe.jail...@wanadoo.fr wrote: Hi,
On Sat, Nov 23, 2013 at 12:00 PM, Rainer Jung rainer.j...@kippdata.dewrote: On 23.11.2013 14:19, Jeff Trawick wrote: (maybe sf already knows something about this) [Thu Nov 21 16:20:17.035427 2013] [:emerg] [pid 1237:tid 47440161182336] AH00017: Pre-configuration failed, exiting Maybe
The current time caching implementation in util_time.c and mod_log_config.c is not guaranteed to work with all compilers and cpu architectures. I have some proposed code I've written, that I want to get input from the mailing list on, before continuing on to compile and test it. The old
I had the same inclination as Cristophe but haven't been able to substantiate anything due to lack of time last week wasn't as kind to my free time as I had hoped. This would be very easy to tweak/test. Within the next day or two I should be able to get back in to perform some rebuilds and do