 |
 |
I currently have the MaxVirtualHosts set to 30000, and I haven't encountered any sort of performance issues. My take would be to just for for it, set it to something that gives you a comfortable cushion above your current usage (if 4200 requires you to keep deleting unused hosts, try setting it to 7000 perhaps?). If for whatever reason it causes issues, it's very simple to set it back to 4200. -Steven On Mon, Nov 28, 2022 at 3:50 PM Hammer, Erich F <[log in to unmask]> wrote: > I'm relatively new to managing (self-hosted) EZProxy, and I have a > question that I'm hoping someone here can help answer... > > Every few days/weeks, I have to manually go into Host Maintenance and > remove hosts that have not been used in over 30 days. That is a PITA for > something that otherwise is fairly pain-free. The documentation explains > how to set the MaxVirtualHosts value and that Proxy by Port (depreciated) > has some limitations, but we have been using Proxy by HostName for a long > time. What the documentation doesn't touch on is twofold... > > 1. How does increasing the MaxVirtualHosts number to something really > large effect performance? > 2. Is there some way to automate the removal of stale hosts? > > Our current MV is 4200. What is appropriate for a sizeable ARL? > > The latter is the more frustrating one. I'm not opposed to writing a > scheduled script to remove stale hosts to automate this, but I have yet to > find any documentation on how to do this from a command/terminal line. > > Thanks for any insight in advance. > Erich > > > -- > Erich Hammer Head of Library Systems > [log in to unmask] University Libraries > 518-442-3891 University @ Albany > > Power corrupts; Absolute power corrupts absolutely; > God is all-powerful. Draw your own conclusions. > -- Steven Marsden Library Systems Analyst, Toronto Metropolitan University Libraries Toronto Metropolitan University (Formerly Ryerson University) [log in to unmask] 416-979-5000 x 554636