Skip to main content

alphaWorks  >  Forums  >  IBM Page Detailer  >  developerWorks

How to restore my PC's response time after using Page Detailer    Point your RSS reader here for a feed of the latest messages in this thread


     

 
 

My developerWorks
 Welcome, Guest
Sign in or register
This question is not answered.

Permlink Replies: 3 - Pages: 1 - Last Post: Apr 29, 2008 9:34 AM Last Post By: LeRoyKrueger Threads: [ Previous | Next ]
DianeHoag

Posts: 2
Registered: Jan 16, 2006 03:19:40 PM
How to restore my PC's response time after using Page Detailer
Posted: Apr 24, 2008 09:17:51 AM
 
Click to report abuse...   Click to reply to this thread Reply
I love Page Detailer, but after using it, my PC is extremely slow. Even the simple typing of text shows delays. Is there some way to restore normal performance to my PC, short of rebooting it (which is what I've been doing)?
LeRoyKrueger

Posts: 31
Registered: May 01, 2006 01:27:16 PM
Re: How to restore my PC's response time after using Page Detailer
Posted: Apr 25, 2008 07:47:17 AM   in response to: DianeHoag in response to: DianeHoag's post
 
Click to report abuse...   Click to reply to this thread Reply
Hi Diane,

I will need to know a bit more about your PC. What version of Windows do you have? I tested Windows 2000, XP, Server 2003 and Vista with all versions and service packs and have not seen a speed problem.

In any case, you can disable the socket stack probe by executing the following on a command line:

wd_ws2i /uninstall

Reboot and Page Detailer will no longer be in your socket stack. To re-enable Page Detailer operation, execute this command from the Page Detailer install directory.

wd_ws2i /install

Any browser you start after this command should be seen by Page Detailer.

If you machine comes back up to speed when Page Detailer is disabled, please get back in touch with me, I would very much like to know what other applications you have. There may be one of them that doesn't deal well with socket stack extensions.
DianeHoag

Posts: 2
Registered: Jan 16, 2006 03:19:40 PM
Re: How to restore my PC's response time after using Page Detailer
Posted: Apr 25, 2008 04:43:48 PM   in response to: LeRoyKrueger in response to: LeRoyKrueger's post
 
Click to report abuse...   Click to reply to this thread Reply
LeRoy,

It appears that this solution requires a reboot, which is what I'm trying to avoid. Rebooting does fix the slowness, but it's inconvenient because I have to close all the applications (mostly browser windows and spreadsheets) that I'm working with, then start them up again after the reboot.

I am experiencing this problem on a standard issue IBM Thinkpad, a T42p. Here's more detailed information:

Microsoft Windows XP Professional
Version 2002 Service Pack 2

IBM Client for e-business
Windows XP version 2.07
Intel(R) Pentium(R) M
processor 2.00 GHz
2.00 GHz, 2.00 GB of RAM

I typically have 10-15 IE browser windows and 5-10 Excel spreadsheets open.

I had the same slowness problem two years ago while running Page Detailer on a different IBM standard issue Thinkpad.
LeRoyKrueger

Posts: 31
Registered: May 01, 2006 01:27:16 PM
Re: How to restore my PC's response time after using Page Detailer
Posted: Apr 29, 2008 09:34:37 AM   in response to: DianeHoag in response to: DianeHoag's post
 
Click to report abuse...   Click to reply to this thread Reply
Oh boy, that is a lot of browsers and spreadsheets.

My best guess about your slowdown is memory related. The Page Detailer layered service provider for the Windows socket stack uses a few bytes (about 80) of thread local memory for each open socket. Since the socket stack is a system service, any storage the socket gets will be locked into RAM. In Windows, an allocation happens in 4K blocks of storage. So I can predict that the Page Detailer layered service provider will take 4K of memory away from your storage pool for each open socket. Each browser window will average 2-4 open sockets. So with 10 open browser windows you would be losing a minimum of 80K of memory (could be much higher if the pages in your browser windows use frames) for your applications. Microsoft Excel also uses sockets for each spreadsheet.

From the above logic, I will say that you usage pattern is very memory sensitive, the removal of some memory from the pool that applications can use is causing the Windows virtual memory system to swap application memory space out to disk. I think that is the source of your slowdown.

You may need to only allow Page Detailer in your Windows socket stack when you want to use Page Detailer. Sorry I couldn't give you a better answer.

Point your RSS reader here for a feed of the latest messages in all forums