|
|
| Author |
Message |
| 25 new of 194 responses total. |
scott
|
|
response 125 of 194:
|
Nov 1 20:33 UTC 1997 |
Grex is now running on a new power supply (courtesy Greg Cronau), so we are
back to full memory and the normal modem card.
That means most modems are back down to 2400 baud, but don't have to wait for
a telnet connection.
|
dpc
|
|
response 126 of 194:
|
Nov 2 03:16 UTC 1997 |
Hooray!! Nice work, people!
|
kami
|
|
response 127 of 194:
|
Nov 2 05:32 UTC 1997 |
Cool! Working nicely, too.
|
blh
|
|
response 128 of 194:
|
Nov 2 12:52 UTC 1997 |
I was impressed with how fast it is working this morning. Thanks!!
|
void
|
|
response 129 of 194:
|
Nov 3 18:08 UTC 1997 |
thanks!
|
n8nxf
|
|
response 130 of 194:
|
Nov 5 22:21 UTC 1997 |
Hot beans! Seems it *was* the power supply!
|
valerie
|
|
response 131 of 194:
|
Nov 10 03:03 UTC 1997 |
This response has been erased.
|
valerie
|
|
response 132 of 194:
|
Nov 10 04:53 UTC 1997 |
This response has been erased.
|
dpc
|
|
response 133 of 194:
|
Nov 10 23:57 UTC 1997 |
Very good news, Valerie!
|
tsty
|
|
response 134 of 194:
|
Nov 11 00:45 UTC 1997 |
please remove those extra unnecessary ptys sot he rest of us can
appreciate some of the relief for a few more days. geeze, this
is the type of profligacy that generates discontent. we kick in
some bucks for improving the EXISTING base of support and faster
than shit, the improvements are dissipated.
so you wnat more support from the EXISTING base again? get it from
the additional 12 pty logins. i've just about had it - and i am NOT
alone, just vocal.
bad news, dpc, not 'good.'
|
valerie
|
|
response 135 of 194:
|
Nov 11 02:47 UTC 1997 |
This response has been erased.
|
dang
|
|
response 136 of 194:
|
Nov 11 03:25 UTC 1997 |
Besides, we're just going back to what we were before we had to use less
memory.
|
jep
|
|
response 137 of 194:
|
Nov 11 14:27 UTC 1997 |
There has been a substantial slowdown for me, anyway, logging in over
the WWW. However, I think it's a wonderful change. It's great to see
more capacity for people telnetting in.
The WWW interface is excellent, by the way. I've used it almost
exclusively for the last few weeks, and it's been very acceptable for
using Grex. I've been using Picospan/YAPP for 11 years from the command
line. I am surprised I could make the transition to the WWW, but I've
done it, and I like it.
|
valerie
|
|
response 138 of 194:
|
Nov 11 21:02 UTC 1997 |
This response has been erased.
|
tsty
|
|
response 139 of 194:
|
Nov 11 23:10 UTC 1997 |
well, with load averages still running in the 16/17/19/20 range,
mho is that the assembled users are overloading the machine ---spreading
too few resources too far. i realize that one root process
running some needed system update or find can slog the load average
all by itself. sure, but that isn't all the time.
i am glad that we are back to 'more ram' -- fine. let us breathe
a while with hte improvement (gasp!) AND the faster link that
is at this moment taking severeal seconds to display my typos.
and india is not here yet ... either.
btw, trying to associate a better power supply to lower load
averages ...ummm, boggles the mind.
if this is faster, i'll take ';slower' -- NewSpeak, ya know?
|
aruba
|
|
response 140 of 194:
|
Nov 11 23:42 UTC 1997 |
Re #139: The association, I think, is that when the power supply was fixed,
staff could add more memory to Grex, which made Grex run faster, which made
the load averages come down. Right?
|
valerie
|
|
response 141 of 194:
|
Nov 11 23:44 UTC 1997 |
This response has been erased.
|
valerie
|
|
response 142 of 194:
|
Nov 11 23:44 UTC 1997 |
This response has been erased.
|
scg
|
|
response 143 of 194:
|
Nov 12 01:37 UTC 1997 |
I think most of us agreed that Grex was way too slow with only 32 MB of RAM.
Once the amount of RAM went up, Grex became nice and fast, probably the
fastest I've ever felt it. It was certainly reasonable to add some ptys.
I think too many were added, though. Grex was slow enough last night to make
me give up on it, and given how long I've stuck through Grex's past periods
of slowness, I'm probably one of our more patient users. I'd be interested
in cutting back, maybe to about half way between where we were before and
where we are now, and seeing how it feels then.
Grex feels plenty fast enough right now, but we aren't full at the moment.
|
valerie
|
|
response 144 of 194:
|
Nov 12 16:45 UTC 1997 |
This response has been erased.
|
e4808mc
|
|
response 145 of 194:
|
Nov 12 21:51 UTC 1997 |
Yes, please cut back a bit. It took 5:37 from login to index with only 3
msgs.
And none of that time was human response time (I have a macro file that gets
me to the first message).
|
jep
|
|
response 146 of 194:
|
Nov 12 22:17 UTC 1997 |
I guess I have to revise my comments, too. Grex has slowed down this
week by a factor of at least 4 for me using Backtalk. There are
multiple-minute waits after entering almost any command (post, next
item, next conference). Backtalk was usable when it was faster, but now
I'm wondering if I should shift back to telnet.
|
valerie
|
|
response 147 of 194:
|
Nov 12 23:56 UTC 1997 |
This response has been erased.
|
i
|
|
response 148 of 194:
|
Nov 13 00:35 UTC 1997 |
Any other parameters, buffers, & whatnot that may need twiddling & tuning?
|
albaugh
|
|
response 149 of 194:
|
Nov 13 19:30 UTC 1997 |
This response is like walking into a bank where there are plenty of windows
to walk up to but not very many tellers servicing them. Better to wait in
line for awhile, with the expectation that you'll be served in a reasonable
amount of time when you do get to the window. Or you can decide that the line
is too long and come back later...
|