Daddy Hobby Forum got software issue?

[nic]

Mike.. is there some kind of memory leak or some other software issue? I noticed DaddyHobby is has very bad response time every now and then, and it seem independant of the number of participants... And every time after a total lost connect (process crash & restart?) then the response time will pick up by a few folds.

[HZM]

I do encounter some prob at times. I do receive some error msg thru email but sorry was really too busy to troublshoot.

Lets hear what others had to say and if is that serious/bad, I will look into upgrading to version 3.01

Mike

[Art]

mike ah...half the time I try to log in from the office it's like that...takes ages to load and stuff...at home it's better....lesser glitches so to speak...

Could it be a bandwidth problem??

[jaZallo]

i think the settings to rich!

make it leaner so more power!

enjoy!

[Jcho]

I have no problem during office hour; problem occurs around 2100 to 0100 hrs. Worst is around 2300 hrs.

[HZM]

Looks like a little hey wire when we got high access during 2200-2300..... Bandwidth likely the culprit


Mike

[nic]

I get it throughout the day..

Here is the results of a ping test from my home PC.

ping -t www.daddyhobby.com

Pinging daddyhobby.com [207.44.218.69] with 32 bytes of data:

Reply from 207.44.218.69: bytes=32 time=522ms TTL=45
Reply from 207.44.218.69: bytes=32 time=550ms TTL=45
Reply from 207.44.218.69: bytes=32 time=576ms TTL=45
Reply from 207.44.218.69: bytes=32 time=577ms TTL=45
Reply from 207.44.218.69: bytes=32 time=563ms TTL=45
Reply from 207.44.218.69: bytes=32 time=508ms TTL=45
Reply from 207.44.218.69: bytes=32 time=495ms TTL=45
Reply from 207.44.218.69: bytes=32 time=536ms TTL=45
Reply from 207.44.218.69: bytes=32 time=508ms TTL=45
Reply from 207.44.218.69: bytes=32 time=522ms TTL=45
Reply from 207.44.218.69: bytes=32 time=508ms TTL=45

Ping statistics for 207.44.218.69:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 495ms, Maximum = 577ms, Average = 533ms
Control-C

C:\WINDOWS>

I will do another one when response time is bad... and we can compare the results... From these we can tell if it is really bandwidth... ;-)

[nic]

Forgot to mention.. there are only 4 active users when I did the pings.