This file contains important information that may not appear in SilkPerformer Online Help. Read this file in its entirety.
For information about installation, deployment, and licensing issues (including the evaluation version of SilkPerformer), see the SilkPerformer Installation Guide.
For an overview of the new features in the current release, see the What's New section below.
| Contents | ||
|---|---|---|
| What's New | Tested Software | Installation Instructions |
| System Requirements | Virtual User Types | |
| Known/Resolved Issues | Getting Help | |
SilkPerformer now supports the testing of Multi-Byte Character Set (MBCS), UTF-8, and EUC-JP encoded Web applications.
SilkPerformer automatically detects the encoding of text during recording and converts all strings to a multi-byte character set format that enables visualization and customization of multi-byte/UTF-8 characters in scripts, logs, reports, parameter files and more.
When a recorded application contains characters that cannot be converted to the currently active Windows system codepage, SilkPerformer scripts those characters in a hex format. A Unicode enabled text/hex editor then assists you in displaying and converting the hex strings.
MBCS/UTF-8 support is also available for SAPGUI testing.
Please refer to "User Guide -> Other Supported Environments -> Multibyte Support" in the SilkPerformer Help for full details.
SilkPerformer now runs on Windows Vista (32 and 64-bit) and supports Vista's User Account Control (UAC).
Please refer to "User Guide -> Other Supported Environments -> Windows Vista" in the SilkPerformer Help for full details.
SilkPerformer now supports dynamic proxy configuration by interpreting PAC (Proxy Auto-Config) files. Dynamic proxy configuration is a technology used by Web browsers to determine a proxy for each request sent out to the Internet. Proxies are dynamically determined based on the URL or host being connected to.
Please refer to the "Proxy options" section of "User Guide -> Configuring Projects -> Project Profile Settings" in the SilkPerformer Help for full details.
JUnit 4
SilkPerformer’s JUnit integration has been updated to support unit testing with JUnit version 4.
Please refer to "User Guide -> Unit Test Integration (JUnit & NUnit) -> JUnit Integration" in the SilkPerformer Help for full details.
JDK 1.6
SilkPerformer now supports the recording of Java RMI applications based on JDK 1.6 and uses JDK 1.6 as the runtime version in Java Explorer.
Realtime Monitoring Datasources
SilkPerformer now supports monitoring of:
Citrix Presentation Server Client 10
Encoding Functions
Web Functions
Each computer that is to be used in a load test must meet the minimum hardware and software requirements listed below.
For details about SilkPerformer performance and scalability, please see the Performance and Scalability Matrix below.
To install agent software, or both controller and agent software, and use the full potential of SilkPerformer to run heavy load-tests, your system must meet the following minimum requirements:
Load Testing
| System Area | Requirement |
|---|---|
| Processor | Pentium IV or equivalent CPU Intel / Athlon Dual Core processor Intel / Athlon 64bit processor |
| RAM | 512 MB (1024 MB recommended) |
| Virtual memory | Three times as much virtual memory as RAM |
| Network | Windows network with TCP/IP (when using remote SilkPerformer agent computers) |
| Network adapter | 10 MBit (fast Ethernet recommended) |
Recording, Monitoring, and Scripting
To use SilkPerformer functionality only for traffic recording purposes, monitoring and scripting, the following minimum system requirements are sufficient:
| System Area | Requirement |
|---|---|
| Processor | Pentium IV or equivalent CPU Intel / Athlon Dual Core processor Intel / Athlon 64bit processor |
| RAM | 256 MB |
| Network | TCP/IP |
To install and use SilkPerformer, your system requires a minimum set of software components.
Supported Operating Systems
SilkPerformer cannot be installed on computers running Windows 95, 98, or ME. Windows NT is not supported.
Other Required Software Components
The specific components that are required vary based on installation type. For example, to run SilkPerformer Java Explorer, your system must be equipped with a Java 2 SDK. All required components are included on the SilkPerformer Installation CD. Components can also be downloaded from their respective vendors' Web sites. See the SilkPerformer Installation Guide for full details.
| Max. # of Vusers per agent |
Web Business App. |
Web Business App. with SSL(-35%) |
Web low level (+20%) |
Recommended #NICs |
|---|---|---|---|---|
| 4xPIII, 1GHz, 4 GByte RAM |
5900 | 3800 | 7100 | 4 |
| 1xPIV, 2GHz, 2 GByte RAM |
4000 | 2600 | 4800 | 2 |
| 2xPIII, 1GHz, 2 GByte RAM |
3600 | 2300 | 4300 | 2 |
| 1xPIII, 1GHz, 1 GByte RAM |
1900 | 1200 | 2300 | 1 |
| 1xPIII, 1GHz, 512 MByte RAM |
800 | 500 | 1000 | 1 |
| 1xPIII, 600Mhz, 512 MByte RAM |
800 | 500 | 1000 | 1 |
| 1xPIII, 600Mhz, 256 MByte RAM |
300 | 200 | 400 | 1 |
Note:
Web Business App uses Page-based Browser-level API (HTML/HTTP)
Web low level uses Browser-level API (HTTP)
Numbers are based on Intel CPUs.
We recommend using single processor agent computers, as they provide the best cost/performance ratio.
Test Parameters:
The numbers of the table above have been determined using a realistic workload with the following characteristics:
The page structure of all requested Web pages corresponds to very popular public Web pages.
The average think-times of all virtual users were about 32 seconds between each subsequent page view, which is a realistic value.
A single virtual user was emulated with 4 concurrent connections, which is a realistic Web browser emulation.
This means that the number of virtual user simulated corresponds to a realistic number of concurrent users accessing a popular Web site resulting in:
Avg. Hits/page: 39
Avg. page size: 130 kByte
Avg. think time between pages: 32 sec
Formula:
Look up the virtual user value from the "User vs CPU" and the "User vs RAM" graph that match the configuration of your agent machines.
From both virtual user values you have received take the minimum value in order to find out how many virtual users your agent machine supports (Web Business App).
Ex: 1xPIII, 1 GHz, 512MB RAM
1) User vs CPU = 2000 vuser
2) User vs RAM = 850 vuser
Min (1, 2) = 850 vuser
-> Agent machines support max. about 850 vuser
For an up-to-date list of resolved defects and known issues/workarounds, please refer to the online Release Notes Add-On.
TopFor an up-to-date list of tested software, please refer to the online Release Notes Add-On.
TopThe available Virtual User Types (VUser Types) Web, Standard, and Premium include the following SilkPerformer application types:
| VUser Type | Application Type |
|---|---|
| Web |
HTTP(S) (Web browser low level) HTTP(S)/HTML (Web browser high level) HTTP(S)/XML (Web services, SOAP) SAP NetWeaver WebDAV (MS Outlook Web Access) Email (SMTP/POP) FTP TCP/IP UDP i-Mode (HTTP) Macromedia Flash Remoting Add-On Streaming Media (MS, Real) DLL Interface |
| Standard | All of Web, plus: .Net Add-On Java Add-On DB2-CLI Add-On OCI Add-On ODBC Add-On (D)Com Add-On Visual Basic Add-On (Framework) Directory server (LDAP) CORBA Add-On |
| Premium | All of Standard, plus: GUI Level Testing SAPGUI Add-On for SilkPerformer Oracle Applications/Forms Add-On PeopleSoft Add-On Siebel Add-On Citrix Add-On Terminal Emulation (Green-Screen) Add-On Tuxedo/ATMI Add-On WAP Add-On |
If you have questions about Borland products or want to contact Borland Technical Support, visit the Borland Technical Support Web site
TopFor information about installation, deployment, and licensing issues (including the evaluation version of SilkPerformer), see the SilkPerformer Installation Guide.
SilkPerformer Results Repository: The SilkPerformer Results Repository has been deprecated. We recommend using SilkCentral Test Manager for storing and analyzing load test results. If you still wish to use the Results Repository, you can download it from the Borland Utilities download page. For further questions, please contact Borland's technical support.
SilkPerformer 2007 needs a new 7.6 license. Due to the change to a more versatile licensing model, SilkPerformer licenses are no longer backward compatible. If you want to run Silkperformer version 2006 or older during the upgrade process to version 2007, you may keep your old licenses for a period of 90 days.
Top