You'll see the time for your health check to the content servers, which is essentially the time for network transfer, from the stats page or socket. Obviously this time will impact the page load times for your client.
Your own metrics for latency via curl or a # time "wget http://contentservers/expensiveresource"; may be valuable. Carlo SysAdmin, Border Stylo On Tuesday, September 7, 2010, Daniel Storjordet <dan...@desti.no> wrote: > Hi! > > Current implementation of HAProxy is working great for us. The other day we > had a server failure without us or our customers' noticing. > > Today our HAProxy solution is hosted on the same location as our content > servers. Unfortunately we have experienced problems with our hosting > companies. Changing the IP for all the domain names for the web pages hosted > on our servers every time we need to switch to a new host is too much work. > > To solve this we wish to relocate the HAProxy servers to a different location > than the content servers. The new host is placed at the backbone of our > countrys internet and the ips can be moved to another host if needed. With > this change we will be able to host our content servers and backup servers at > any location and can move them around without updating all the domain names > every time. > > However we are concerned about the performance penalty of hosting the HAProxy > servers at an different location that the content servers. Are there any > statistics on what kind of performance penalty we will receive, and any other > unforeseen effects this might have? > > > -- > mvh. > > Daniel Storjordet > > D E S T ! N O :: Strandgata 117 :: 4307 Sandnes > Mob 45 51 73 71 :: Tel 51 62 50 14 dan...@desti.no :: http://www.desti.no > www.destinet.no - Webpublisering på nett > www.func.no - Flysøk på nett > > >
