I am running SilkTest 5.0 under 200 Mhz WindowsNT 4.0 with 64MB in one PC and 128 MB in another. With both of these, I have a number of issues when I record and playback scripts. Sometimes the agent stops responding. Sometimes the browser becomes too slow. (I am trying to findout a pattern for this so that I can report this to Segue)
* Has any of you seen this annoying behavior of Silk?
* Any tips on what processor/memory combination that works satisfactorily?
Yes I had both those things happen to me as well. Unfortunately I cannot pin down exactly what I did to make it better.
I had been useing Silk Extensions (through Silk->Options->Extensions
And I set Netscape 4.0 and IE 4.0 through this interface. Also I had IE desktop and I followed Segue's instructions to de-install it.
Then I discovered that Netscape and IE cannot be run simultaneously through the same script session. So I disabled IE through:
Start->Programs->Silk Test->Extension Enabler
AFTER I disabled IE through
Honestly don't know why but things got way better. I will be watching the forum on this one, I really want to pin down what went wrong THIS TIME.
"Smoke me a kipper, I'll be back for breakfast!"
Sr. QA Engineer
[This message has been edited by rick_weth (edited 09-18-1999).]
Performance problems may also be due to memory leaks with
Silk and the browser, which I ran into over very long
test runs. Below are a few articles from a thread on this
earlier this summer.
From: Terry Horwath
Sent: Wednesday, June 30, 1999 6:48 AM
Subject: Silk 5.0/Netscape 4 memory leak
If you are encountering intermittent/strange failures during
long (3+ hours) test runs using Silk 5.0 and one of the Netscape 4
browsers (4.08 or 4.51) you are likely running out of
memory. I have finally tracked this problem down, under NT 4.0. This
problem does not appear to occur using Navigator 3.04 gold.
The problem is obvious once ALL of physical memory is consumed,
as you get virtual memory error dialog. But it is not at all apparent
as you get close to exhausting memory (ah, those boundry conditions, eh?).
The cause of the virtual memory error is Navigator -- it slowly
consumes all of available memory, which appears to be a memory leak
problem. But its not clear to me if Navigator is the real culprit or
the Silk Agent's integration with Navigator. I have logged a problem
with Segue support.
Netscape's 4.x browsers are prone to memory leaks standing by themselves. On more than one occasion, I've left a Netscape browser open overnight or over the weekend, doing absolutely nothing but sitting on a home page and it's eaten up all available memory. It is possible that working these browsers in conjunction with Silk accelerates this process.