A great idea. I have added the copy code to a startup block, logged the results in a table the user (should be terminial), elapse time and a time stamp. From this you can get up to all sorts of tricks calculating averages for the user and the site. If the results are out of spec the application can issue Email warnings. Early days yet but the results look promising.
Thanks for the tip. Ian At 13:52 12/12/2001 -0700, you wrote: >Thanks for the advice. We are going to do this test. I'll let you know >how it goes. Tricia > > >>> <mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED] 12/11/01 12:41PM >>> >Yes Bill, > Last week my accountant called and said another of his clients was trying >to talk him into upgrading his server hardware to a 1Ghz+ box (its just a >file server) because he was experiencing some dreadfully slow updates on a >few workstations (even in a word processor). The "Fix" according to the >other guy was going to cost him $6000. I told him to go workstation to >workstation and copy a 4MB file from the server and then back to the server >and time it. 7 of the workstations took about 15 seconds, 2 of them took >about 9 Minutes. This is for sure a NIC or cable (I had him swap the cables >in the hub to make sure there wasn't a hub port bad) and a helluva lot less >than $6000. Many times just because we are able to get a network connection >and use it, we are quick to accept that it is OK when it may be far, Far >from being optimized. > >Mike >----- Original Message ----- >From: "Bill Downall" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Tuesday, December 11, 2001 12:18 PM >Subject: RE: Frustrated user > > > > Dan, > > > > Tricia has that problem, but she also has some other problem in the > > huge delay when R:Base starts. > > > > Some of the things that have helped beat those long delays at > > CONNECT for other R:Base users on Novell have been: > > > > Use the MS Client on the workstation, not the Novell client. > > > > Remove extra, unnecessary protocol bindings in the "network > > neighborhood" settings. > > > > Check for faulty network wiring or connecters or NIC cards or hubs. > > > > Replace hubs with switches. > > > > Set your antivirus software to exclude from checking *.rb1, *.rb2, *.rb3, > > and *.rb4 files > > > > Bill > > > > On Tue, 11 Dec 2001 08:47:09 -0800, Dan Goldberg wrote: > > > > >When you go to version 6.5 and up R:base does not user the > > server6.rbg file anymore!! All those problems will disappear!! > > > > > >No more admin program!! > > > > > >No more resetting the server6.rbg file!! > > > > > >Dan > > > > > > > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > > > >================================================ >TO SEE MESSAGE POSTING GUIDELINES: >Send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: INTRO rbase-l >================================================ >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
