On Wed, 2006-02-08 at 22:25 -0800, Howard Chu wrote: > I'm seeing a significant amount of CPU use after a search completes, > apparently just from updating the op counters. The CPU really should not > be 50-90% busy after processing a single query, after the client has > already disconnected. I think it might be better to prefer long long's > to the bignum or gmp stuff. Are we really concerned that any 64 bit > counter is going to overflow? Even on 10Gbit ethernet it will take ~544 > years to overflow a 64 bit byte counter, and that's assuming a > continuous output stream at 100% bandwidth utilization.
The reaon that stuff was introduced is essentially the byte counter would wrap in hours with a 32 bit long. I guess this can be disabled, or made a configure option that's "no" by default. How can you explain that excessive load? GMP is supposed to be pretty efficient (I can't say anything about BIGNUM). p. Ing. Pierangelo Masarati Responsabile Open Solution OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: [EMAIL PROTECTED] ------------------------------------------
