Pearl.exe Rapes Processor and Sucks Memory

| Comments | 0 TrackBacks
Faramarz and I were baffled, there's a server resource (pearl.exe) hogging the processor on our Windows Server.

When a server slows down, my first reaction is to launch taskmgr.exe to see who's responsible for this debauchery. I notice Pearl.exe raping the processor to 100% and sucking a large chunk of memory.

Picture: taskmgr.exe


Pearl.exe is assigned to our Movable Type websites. We have about 10 of these sites, each share this resource.  Operative word: share. When a website goes crazy on a certain resource like Pearl.exe, the processor works extra-hard and the memory consumption extra-high, unfair to other resources. 

So what the frack, who's doing this? Each website belongs to a client and their client, impossible to identify the latter, I decide to find the greedy website (our client).

The plan: Give each website a unique User ID/Password with anonymous privileges. Without anonymous privileges, the user surfing the website from their internet browser won't have access, not without credentials.

The Method: (IIS, Folder Permissions, Resource Permissions, to inheirit, or not inheirt, creating ID's, Groups)

No TrackBacks

TrackBack URL: http://52weeks.ca/PP/mt-tb.cgi/36