Kami ay nagtatrabaho sa isang testing user pagtanggap (UAT) kapaligiran na, kumpara sa pag-unlad, ay patay mabagal.
Ito ay isang komplikadong kapaligiran gamit ang FBA, SQL 2008, SSRS at pinalawig na mga web application naa-access sa internet gamit ang https, kaya ito ay naging mahirap upang subaybayan ang down na ang isyu.
Para sa isang nakaraang client, we used FBA with an LDAP role provider (and membership provider). One of my colleagues, far more clever than I, determined that the "out of the box" LDAP role provider, when used in that environment, wasn’t scaling well. To solve this problem for that client, he implemented a nice caching scheme in a custom role provider.
This situation seemed similar, so we looked into replicating that solution to the today’s client. As I was debugging that, I noticed that this message would frequently appear in the System log (from 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.
I took this to mean that the app pool was recycling far, malayo masyadong madalas at nais na ipaliwanag ang isang pagganap ng problema.
I looked at the app pool’s properties and its "Recycling" page showed that the property "Maximum virtual memory (sa megabytes)" 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" na ang nangyayari sa doon, ngunit malinaw na ang ilang mga uri ng mga dahilan / epekto bagay ang nangyayari at para sa ngayon, ang UAT kapaligiran ay kapaki-pakinabang.
</dulo>
Phil Wicklund