Hi Walter, You’re right, this is going nowhere. We thought that the bottleneck might be the http connection between the API running on Cloud Foundry, and the Solr Cluster on an external host. Potentially saving bandwidth on that seemed (at the first glance) like a too good option to not look into.
I just would have liked to see that confirmed in a performance test, but after discussing it again with our sysadmin I don’t want to waste any more of his or my time trying to make that work. Ah well, at least I learned a few things about Solr :) Thanks for your comments. Lúthien > On 27 Feb 2019, at 17:08, Walter Underwood <wun...@wunderwood.org> wrote: > > I really do not expect it to make anything faster. I think you are wasting > your time. Compression also adds some latency because the compression happens > before data is sent out. > > If your CPUs are idle, that is a red flag for performance. In every one of > our clusters, CPU is the limiting factor in both latency and throughput. Our > largest production cluster is 32 nodes, each with 36 CPUs. > > Where is the bottleneck? Are the processes waiting on disk? If they are, you > need more RAM. Do you have magnetic disks? Get SSDs. > > You should have enough RAM to hold the index in memory, after allowing for > the Solr JVM, kernel, and other processes. -- Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. If you are not the named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.
