Tá muid ag obair i tástáil ghlacadh úsáideora (UAT) timpeallacht a, i gcomparáid le forbairt, Is é marbh mall.
Tá sé an timpeallacht chasta ag baint úsáide as FBA, SQL 2008, SSRS agus iarratais gréasáin inrochtana sínte ar an idirlíon ag baint úsáide as https, mar sin tá sé deacair a rianú curtha síos ar an tsaincheist.
Do chliant roimhe, a úsáid le linn FBA le soláthraí ról LDAP (agus soláthraí ballraíocht). One of my colleagues, i bhfad níos cliste ná mé, determined that the "out of the box" Soláthraí ról LDAP, nuair a úsáidtear sa timpeallacht, wasn’t scaling well. To solve this problem for that client, he implemented a nice caching scheme in a custom role provider.
An staid seo an chuma den chineál céanna, so we looked into replicating that solution to the today’s client. As I was debugging that, Thug mé faoi deara go mbeadh an teachtaireacht seo le feiceáil go minic sa logáil Chóras (ó Viewer Imeacht):
A worker process with process id of ‘XXX’ serving application pool ‘Home – 80’ has requested a recycle because it reached its virtual memory limit.
Ghlac mé seo a chiallaíonn go raibh an linn snámha app athchúrsála i bhfad, i bhfad ró-mhinic agus go mbeadh a mhíniú fadhb feidhmíochta.
I looked at the app pool’s properties and its "Recycling" page showed that the property "Maximum virtual memory (i meigibheart)" 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" sin ag dul ar aghaidh ansin, ach go soiléir go bhfuil roinnt de chineál ar chúis / éifeacht rud ag tarlú agus do anois, Is é an timpeallacht UAT inúsáidte.
</deireadh>
Phil Wicklund