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 is now tightly integrated with SilkTest, Borland’s functional testing tool, and supports load testing of applications
on the GUI level. Applications that are not supported by SilkPerformer on the protocol- or API-levels can be tested by running
multiple SilkTest-GUI virtual-users per agent machine in different Windows Terminal Services sessions. SilkPerformer automatically
creates terminal server sessions and deploys SilkTest scripts to the agents where the scripts are executed. SilkTest launches clients,
runs GUI-level tests, and communicates test results back to SilkPerformer. Terminal server sessions are closed automatically once load tests are complete.
Please refer to the “GUI-Level Testing Support” section of the “Other Supported Environments” chapter in the
SilkPerformer User Guide for full details.
SilkPerformer 2006 R2 is packaged with a plug-in that enables Eclipse users to develop and debug SilkPerformer Java Framework
scripts using the powerful Java IDE. With the plug-in, you can execute TryScript runs for Java test classes and explore the results
directly in Eclipse. After creation, test classes can be seamlessly passed on to SilkPerformer where they can be used for load tests.
Please refer to the “SilkPerformer Plug-In for Eclipse” section of the “Other Supported Environments” chapter in the SilkPerformer
User Guide for full details.
Real-Time Client-Side Measures
Silk Performance Explorer now supports real-time monitoring of client-side measures such as transaction timers, page timers, and custom
timers for virtual users. This enables you to react quickly to response-time issues during load tests, saving you time and simplifying tune-up operations.
Please refer to the “Enabling Real-Time Client-Side Monitoring” section in the Introduction of the Performance Explorer User Guide for full details.
JMX
SilkPerformer's support for JMX (Java Management Extensions) monitoring enables you to browse and monitor MBean (Managed Bean) attributes that
are exposed by Java application servers. Attributes that return numeric data can be added to Performance Explorer monitors as data sources.
The JMX Data Source Browser enables easy filtering and browsing of MBeans. Preconfigured JMX queries (Easy JMX) provide access to the most
important attribute values of MBeans that are hosted on JMX MBeanServers.
Preconfigured JMX queries are available for:
Please refer to the “JMX Monitoring” section of the “Monitoring Servers” chapter in the Performance Explorer User Guide for full details.
A new Results tab in SilkPerformer’s Workbench offers full control over your test results. It displays a tree view that contains all test
results of the currently active project, including TryScript run results, load test results, and SilkCentral Test Manager test-definition
results (if your SilkPerformer project is linked to a Test Manager test definition).
Through enhanced integration with SilkCentral Test Manager, you can now upload specific SilkPerformer results to Test Manager by
right-clicking a results node in SilkPerformer. Or you can download the results of multiple Test Manager test executions to the SilkPerformer
Workbench. Load-test results are now automatically stored in uniquely named subdirectory folders.
Please refer to the “Exploring Test Results” chapter in the SilkPerformer User Guide for full details.
SilkPerformer now provides an API function for Web application testing that suppresses password exposure in TrueLog files.
SilkPerformer 2006 R2 uses version 0.9.8a of the OpenSSL library.
Java Explorer now supports the testing of secure Web services. Users can select between Axis 1.1, 1.2.1, and 1.3 Web service stacks.
SilkTest Automation Functions
Web Functions
String 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: 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 2006 R2 needs a new 7.5 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 2006 R2, you may keep your old licenses for a period of 90 days.
Top