https://bz.apache.org/bugzilla/show_bug.cgi?id=69841
--- Comment #7 from Ákos Szőts <[email protected]> --- This new version is definitely a step in the right direction: with timeout value of 5 seconds, there're no more "mutex busy" prints. With 0 timeout, the mutex busy prints are still there, so caching is effectively not done, but the crash is avoided. It's also a bit slower than with a reasonable timeout. What I think is still missing is the caching of the encrypted password. How I _think_ requests are done now is like: 1. Receive a request from the UA with clear text password 2. Apache runs the password through crypt() that takes a considerable amount of time for modern encryption. No caching is done at this step. 3. The now-encrypted password is checked against the cached value from the DB (that stores the password already encrypted). 4. Request is served after a successful encrypted==encrypted comparison The slowness comes in at step 2. Apache runs crypt() on every single request without caching it and crypt() is (and should be) slow. I recorded a short screen capture to visualise that it takes 5 seconds for a local website to serve 1.1 MB of data via 77 requests. Bugzilla didn't allow me to upload this file, so I placed it here: https://mega.nz/file/pcgGhCLK#RhtpQPohoxPRctrfpx4Zjkrp4ClXo0zMgJuJzQVAjBA -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
