|
SPECweb99_SSL Support FAQLast Updated: October 24, 2003 |
The following two simple steps can answer 90% of SPECweb99_SSL technical support questions:
Thu May 4 17:50:41 2000 Empty Deck Thu May 4 17:50:41 2000 Generating Deck Thu May 4 17:50:41 2000 Randomizing Deck Thu May 4 17:50:41 2000 Empty Deck [ . . . ]
"Can't locate WebClient.pm in @INC
(@INC contains: C:\SPECweb99_SSL\bin C:\SPECweb99_SSL\bin\lib/MSWin32-x86
C:\SPECweb99_SSL\bin\lib C:\SPECweb99_SSL\bin\lib\site .) at ..\manager line 107.
BEGIN failed--compilation aborted at ..\manager line 107."
"Can't locate Getopt/Std.pm in @INC (@INC contains: < . . . > .) at manager line 114. BEGIN failed--compilation aborted at manager line 114."
Checking dynamic POST with
'http://myserver/fast-cgi/spec99fcgi.fcgi?/file_set/dir00043/class1_4'
**ERROR**: Improper file returned. See dynpost.out for returned text
**ERROR**: There should only be 1 post log entry;0 were found
NOTE: errors in dynamic POST may be caused by problems in
command/Reset. Check that the post.log gets zeroed correctly
From dynpost.out, the error message from the cgi (which depends on your cgi
or course) said it was called with no parameters.
$req->header('Content-type' => 'application/x-www-form-urlencoded');
The updated block of code should now read:
if ($operation =~ m/POST/i) {
$req = new HTTP::Request 'POST' => $url . "f";
$req->header('Content-type' => 'application/x-www-form-urlencoded');
my($urlroot) = ($url =~ m#\?(.*file_set/)#);
$req->content("class=1&client=2&dir=00004&num=3&urlroot=$urlroot");
}
Note, the client code already includes the Content-type for POSTs. Checking dynamic custom ad (CAD) GET with 'http://xxx/scripts/specweb99-cgi.pl?/wwwroot/file_set/dir00024/class1_2' **ERROR**: Improper file returned. See dyncadget.out for returned text **ERROR**: No Custom Ad substitution was found -- see runrules for information on the WEB99CAD string substitution NOTE: errors in Custom Ad Rotation may be caused by problems in command/Reset.
Check that upfgen and cadgen get run correctly
If running the Perl cgi is the bottleneck, then you can check the published SPECweb99_SSL results and see if anyone has used the same webserver software that you are using. If so, you may be able to use one of the API implementations that have been submitted to SPEC. See the SPECweb99_SSL Dynamic API Sources at http://www.spec.org/web99ssl/results/api-src/. Alternately, you may wish to implement the dynamic content using your API of choice following the implementation as defined in the detailed pseudo code that appears in the Run and Reporting Rules.
Try looking at the published results to see the type and number of clients and how they are networked into the server. Then, take one of the clients you have available and determine how much load it can drive and still have roughly 20% idle cycles on the client. Then, make the best guess at how many simultaneous connections the server can do. Then, divide that by your single client value to get a rough estimate of the number of clients you'll need.
To install the new manager:
