Radili smo na testiranje korisnika prihvaćanje (UAT) okolina koja, u odnosu na razvoj, je mrtav spor.
To je komplicirano okruženje pomoću FBA, SQL 2008, SSR i proširene web aplikacija dostupnih preko interneta putem https, tako da je bilo teško pronaći pitanje.
Za prethodni klijent, koristili smo FBA s LDAP uloga davatelja (i članstvo usluga). One of my colleagues, daleko pametniji od mene, determined that the "out of the box" LDAP Uloga usluga, kada se koristi u tom okruženju, wasn’t scaling well. To solve this problem for that client, he implemented a nice caching scheme in a custom role provider.
Ova situacija se činilo slično, so we looked into replicating that solution to the today’s client. As I was debugging that, Primijetio sam da je ova poruka često će se pojaviti u sustavu zapisnik (iz Event Viewer):
A worker process with process id of ‘XXX’ serving application pool ‘Home – 80’ has requested a recycle because it reached its virtual memory limit.
Uzeo sam to znači da app bazen je recikliranje sada, daleko previše često, a to bi objasnilo problem performansi.
I looked at the app pool’s properties and its "Recycling" page showed that the property "Maximum virtual memory (u megabajta)" had been set to true and had been set to 5000. That seems like enough, but I decided to unset the value and that had an immediate positive effect. No more app pool recycling. No more mysterious slow-downs and pauses.
I don’t really understand the underlying "stuff" da se tamo događa, ali jasno nekakav uzrok / učinak stvar se događa, a za sada, UAT okoliš je korisna.
</kraj>
Phil Wicklund