Neil,
The hit count I was referring to was on our webserver. The voipwx.net
domain. I was not talking about our dedicated WX-TALK conference
server which resides at a separate data center connected directly (un-
throttled)to an OC3 and neither the cpu, memory or bandwidth demands
exceeded an idle during yesterday's event.
We peaked at 3:05pm ET yesterday with 38 direct connections. Of
course many of those were other conferences linked in with their own
connections. Our maximum TX bandwidth rate was only 626 kbps, which a
single T1 could have handled just fine.
I'm not sure why you had any connection problems but I did
hear that a few others did early on as well. The individual load on
any given conference server has no effect on the overall echolink
system. There may have been an issue with the echolink addressing
servers for a while which sure could have caused connection problems.
FYI - We ended up getting 8110 hits on the website by the end of the
day, which is not too bad for it's second day of existence. :-)
I've changed the format of the site just a bit this morning and I'm
sure it will continue to evolve with time. We just needed an
immediate presence to begin with.
Regards,
Kevin Anderson
KD5WX
