New sever install - Delay loading websites

[SteveB_NI]

New server install complete - 4 VMs on Hyper V on one server - all running Server 2019.

 

Now noticing that our initial load of websites is very slow - no matter what time it's accessed, or no matter what load currently on the server. Once the initial site is loaded, it runs ok from that point onwards - as in all the links within that site - until I browse to another website.

 

Any ideas how to investigate where the bottle neck is here? VMs are all allocated variable dynamic RAM and this isn't being anywhere near maxed out - 6GB available etc.

[DGardiner]

sounds like a dns issue or authentication on the proxy to me

 

try running nslookup and see what lookup times are like there

[Steve21]

Is that just the 1st load per reboot, or the 1st load for every website every time someone accesses it?

 

IIS doesn't reload pools until they're accessed, and then will auto recycle them after certain periods of downtime which can be configured in the pool/site settings

 

This is assuming you're talking IIS rather than external browsing ? etc

 

Steve

[mavhc]

Is this on all clients? All browser? Do you have automatic proxy detection on? Is that set up correctly?

 

Does ping work fast? nslookup?

[SteveB_NI]

Hmmm - this is interesting.

 

I can ping both DCs from a client workstation, and get a quick response. I can also successfully ping the router.

However, when I ping Google for example I get a response back saying request times out. Which is bizarre as I'm able to browse to Google no problem - as the proxy address works fine.

[mavhc]

Does it resolve google.com to an ip? What happens when you tracert that ip?

[3s-gtech]

Does your firewall actually allow ping through? I can't ping external websites for that reason.

 

Otherwise, you may have an odd/missing gateway configuration on the NICs?

[SteveB_NI]

Does your firewall actually allow ping through? I can't ping external websites for that reason.

 

Otherwise, you may have an odd/missing gateway configuration on the NICs?

 

Good point - you're right - no pings can actually pass through.

 

The IP config as sent by DHCP is:

Gateway - proxy address - CensorNet CloudUSS

 

then 2 x DNS servers - both the DCs. Everything pings fine.

[3s-gtech]

You mention dynamic RAM, what about the disks? I've found dynamically expanding disks can cause some odd performance issues Hyper-V Dynamic Disk Pros and Cons

[mavhc]

if you can't ping as a test, try powershell's invoke-webrequest, or curl as it's aliased to

[SteveB_NI]

Thanks for the pointers all. I switched off the dns role on the existing server and it stopped working all together. Therefore it seems to be relaying back to that somehow before displaying final pages. This would likely explain the delay.

 

I’ll dig deeper into it when I get a chance again - thanks again for your help