I understand that our conference call on Monday morning is canceled. ITS re-booted ilssv4 today, 1/17. We've now completed all the tasks that EISI requested in response to our trouble ticket.
It sounds like you've made progress in preparing for testing. You said you might be ready to test on Wed. or Thurs. Should we have another call before then or do you want to go ahead with your testing and then report on it? FYI, we have a small test database on ilstest1 where we're currently testing Voyager 6.2. I just wanted you to know so that you, Eric Banks, and those of us at LC who are working on that box don't collide.
Please let us know how you'd like to proceed and if there's anything we can do to help. Thanks for this detailed status report.
>>> "Rasey, Josh (END-CHI)" <[log in to unmask]> 12/15/06 5:20 PM >>>
A couple of quick updates:
1) Unfortunately I will be out Monday (This came up at the last minute,
I do apologize.)
2) The Z3950 test script MAY turn out to have more functionality then I
had originally hoped for.
1) We should be able to launch up to 100-150 parallel queries.
2) Timing will be available for each search
3) The results will be available as well
1) I wrote this in Perl, using the ZOOM module (Net::Z3950::ZOOM)
which relies on some YAZ development libraries.
2) This is problematic as I am also using Perl threading, which is
not enabled by default in our distributions.
3) Having to have the ability to compile YAZ and a Thread enabled
Perl will most likely limit it's portability.
I still need to do true scalability testing, I have confirmed this works
from 1-10 searches, so I should have this ready by the end of Tuesday.
Assuming this all checks out, we should be able to load the test server
Wednsday-Thursday and see if we can recreate the conditions found on the
Joshua J. Rasey
Manager, Digital Technical Support
Endeavor Information Systems Inc.
1350 E. Touhy Avenue
Suite 200 East
Des Plaines, IL 60018
Direct Line: 1-847-227-2961