https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11974 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #29 from David Cook <dcook@prosentient.com.au> --- I am very interested in this, as I've been saying for a while that it would be good for Koha to use Unix sockets instead of TCP sockets when running on the same host. I learned a lot reading the comment section, and I'll do some experimenting locally. For what it's worth, I've seen huge 100% speed improvements with PostgreSQL when using Unix sockets over TCP sockets for apps that abuse the database far worse than Koha. I think it's a universal truth that socket speed works like this: Unix Socket > Localhost TCP Socket using loopback device > External host TCP Socket. In the case of Localhost TCP vs External host TCP, I've seen other apps see 600% performance improvements when dealing with the thousands/millions of records. On an individual per record basis, the performance improvement might be a fraction of a second, so the improvement looks very small, but when you aggregate up the time savings can be *massive*. It depends on your workload. -- You are receiving this mail because: You are watching all bug changes.