Proget 5.3.35 slow in Browser (Cache)

dac_4595

Hello,

We use proget 5.3.35 mainly with nugets. I can access the Website with a browser(chrome) and it will run fast. I will revisit the site the following the next work days.
Meanwhile the browser has been closed or even the machine did reboot. After about one day the website will become really slow 5-10 seconds to access one package.

I can access the website from the same machine with another browser and i will have no problem. We are using active directory authentication

Clearing the cache in the browser with devtools or via setting will solve the problem. Website will be very fast again. Package and Feeds open in under one second.
Any ideas what todo?
In case it might be a bug, what information can i provide.
At least we found that workaround.

Best Regards
Dario

atripp

Hi @dac_4595 ,

If ProGet is hosted in IIS, then one thing that might be happening is that Application Pool shuts down if it's not accessed in a set amount of time. That 5-10 seconds might be the initial start-up time. You can control the timeouts in IIS, and even set it to be AlwaysOn.

Otherwise, there's nothing in the browser's cache that would cause this. If anything, clearing the cache would cause things to go slower, as pages need to re-load.

Cheers,
Alana

atripp

Generally speaking, if yo ucan try to identify the pattern -- like which pages are slow -- that will help.

Some different pages to investigate:

/ is somewhat resource intensive, and involves database calls
/health uses minimal system resources
/resources/images/layout/logo.svg is a static image, is unauthenticated, and is cached by the browser

dac_4595

Hello Alana,
Yes my first guess was also application Pool shutdown and wakeup. Thats not the problem as the website will stay slow all the time. Also its reproducable that two browsers on the same machine work with completly different speed.

I will provide logs of the page you mentioned when i run in that problem again. Clearing cache did reproducable solve the problem. Of course the first call might take a second longer, but after that it works fine.

Best Regards
Dario