Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
voipwx.net hit count
John
Kevin,
toggle quoted message
Show quoted text
That's great for the first day. I was out of town for the day so couldn't participate John Kevin Anderson wrote: As of 3pm CDT we have received 5575 hits today alone on our new website. Looks like word has gotten out. --
John Mc Hugh, K4AG Coordinator for Amateur Radio National Hurricane Center, WX4NHC Home page:- |
kf4vgx
ITS not my fault :)
toggle quoted message
Show quoted text
In VOIP-WXNET@..., John <K4AG@a...> wrote: Kevin, |
Neil Lauritsen
开云体育?
The large number of users caused a few minor VIOP
problems on the Internet when I first
logged on, but then after getting disconnected several times, everything worked
extremely well.
I have a DSL connection so I did not experience
any audio glitches. The audio quality at my connected speed was
excellent?
73,
?
Neil W4NHL ?
|
kf4vgx
No problem here,
Jonathan Taylor stated in a Net . That with 2000 user's . Echolink would only pull about one quarter of what it can actually support. 73 KF4VGX In VOIP-WXNET@..., "Neil Lauritsen" <neil-w4nhl@v...> wrote: Internet when I first logged on, but then after getting disconnected several times, everything worked extremely well. I have a DSL connection so I did not experience any audio glitches.The audio quality at my connected speed was excellent 73, |
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 |
to navigate to use esc to dismiss