- From: Laird, Brian <BLaird@perseco.com>
- Date: Tue, 20 Apr 2004 16:36:35 -0500
- To: "Yves Lafon" <ylafon@w3.org>
- Cc: <www-jigsaw@w3.org>
- Message-ID: <45A6279F82E4CA4BBDC0F4EFC7B6A2FE127FA3@atlas.perseco.com>
Hey Yves, First, I have been running off the build you made a few weeks ago and everything has been great. From our standpoint, everything seems to be caught up and fixed. Thomas deserves a huge thank you for putting together SSL fixes. His solution is much more elegant and useful than what I had originally came up with. Now what email from wouldn't be complete with a few issues / questions: 1) Re-indexing loses changes made to a file entry: I setup an existing html file, which was originally indexed with an HTMLFrame, with the SSIFrame. If I re-index through the admin tool, the SSI Frame and subsequent filters are lost and reset to the HTML Frame. Is this correct and is there any way to correct it so that doesn't happen? 2) Performance of the mirror frame: We have been doing a lot of load testing on our jigsaw servers and I have figured out that on a per request basis the mirror frame takes at least 2 seconds to do it works. An example would be the following: * Workstation talks to server1 to be mirrored - We get 250+ requests per second for a 1 user load (no think time) * Workstation talks to jigsaw server which is mirroring server1 - We get about 40 requests per second. It should be noted that jigsaw does great just serving up files. I am hoping that you can help shed some light why there is such a gap when doing the mirror frame or if there is settings we can use to optimize the performance. I do realize everything that has to be done in mirror frame and I also realize that in the long run there may not be anything that can be done about it. This could also be more of an issue with HTTP client and less with the mirror frame. Let me know what you think or if you have more information that might help me. Thanks again for all the help. Brian ************************************************************************ This e-mail and any accompanying documents or files contain information that is the property of Perseco, that is intended solely for those to whom this e-mail is addressed (i.e., those identified in the "To" and "Cc" boxes), and that is confidential, proprietary, and/or privileged. If you are not an intended recipient of this e-mail, you are hereby notified that any viewing, use, disclosure, forwarding, copying, or distribution of any of this information is strictly prohibited and may be subject to legal sanctions. If you have received this e-mail in error, please notify the sender immediately of any unintended recipients, and delete the e-mail, all attachments, and all copies of both from your system. While we have taken reasonable precautions to ensure that any attachments to this e-mail have been swept for viruses, we cannot accept liability for any damage sustained as a result of software viruses. ************************************************************************
Received on Tuesday, 20 April 2004 17:37:21 UTC