Gebsbo wrote:

Computer: XP Pro

Thought id try the new Byond. I ran it for no more than 20 minutes and with 6 players or less everything runs fine. Once you have 7 or more players everything to starts to lagg abnormally, with lagg lasting for abnormal ammounts of time.

I had the profile and CPU being monitored all the time. CPU jumped to over 125% for more than 20 seconds before i had to pull the server off. Ive been testing all week so i can say that this laggs not because of my lame hosting lol. Thought id report this.

Thanks for your feedback. Falacy was running this with 30+ players yesterday on a Windows system without incident, so this is a contrast to his report. It would definitely be helpful to know if we need further tweaking. I have some followup questions:

1) What kind of Internet connection do you have?
2) What kind of processor does your computer have?
3) How much memory do you have?
4) What else were you running on your computer at the time?
5) In the task manager, what does the CPU usage for dreamseeker.exe or dreamdaemon.exe (whichever you use) look like? What about memory usage?
6) Which game were you hosting?

Tom wrote:

Lummox JR wrote:

1) What kind of Internet connection do you have?

2MB i think

2) What kind of processor does your computer have?

1.6GHZ although i usually host on my 800Mhz to test the games efficiency

3) How much memory do you have?

1GB

4) What else were you running on your computer at the time?

Messenger

5) In the task manager, what does the CPU usage for dreamseeker.exe or dreamdaemon.exe (whichever you use) look like?

Usuually 1 - 30
What about memory usage?
16k

6) Which game were you hosting?

Shaman King Online 2

Also, under the same conditions, how does v.462 perform?

I hosted under 462 and the game was able to hold more players before the same thing happend again. I then investigated further with some help of Mr Falacy and it seems some sleeps and set background declarations in procs were the cause. So im gueesing its a false alarm.

The point is, if it worked on the old machine in the last version, but not this one, there might be a problem with the new version.