PtokaX forum

Development Section => LUA & PtokaX-Scripting-Interface => Topic started by: piglja on 12 October, 2003, 11:37:07

Title: Hmm, a question to Developers
Post by: piglja on 12 October, 2003, 11:37:07
Hmm, as I remember - IceCube was the most stable and less eating CPU release...

What is wrong with new ones?:) Maybe there is something changed in the code what is slowing down PX itself?

I am just VERY curious... Because I can not keep more than 1k users on my hub, my PC is getting crazy, it is on 80-100% CPU usage all the time, and it is not bandwidth...

Thanks:)
Title:
Post by: [NL]Pur on 12 October, 2003, 13:41:53
well, i think it has something todo with userstats,
performance is better when disabled.
Title:
Post by: [ES]latinmusic on 12 October, 2003, 18:51:31
QuoteOriginally posted by piglja What is wrong with new ones?:)
Bugs and old bugs still present in lastest releases thats becomes out. All versions of ptokax have new adds so is a normal process very deep bugs comes out now and make the program unstable. The new stuff implemented in the last versions about multihub and statistics becomes ptokax unstable, also there was some problems presents related to the API.
For the incoming version you have to expect a ptokax based in a new rewrite core and critical bugs fixed, also the develop proccess is centry in less cpu/memory resources and stability for a large amount of users connected into the hub. All this means PtokaX will set a new high line for hub servers one more time.
Title:
Post by: plop on 12 October, 2003, 19:35:49
QuoteOriginally posted by [NL]Pur
well, i think it has something todo with userstats,
performance is better when disabled.
were not using the userstats from ptokax as my ai bot has it's own database.
but we are suffering from the same thing as piglja, on 700 users it runs fine but 750 causes lag.
again the bandwidth is no problem (100Mbit).
have 2 say it can be a bug also in ai as odin this morning reported the same problem on his hub (350 users, uptime 14 day's), didn't disapear on deleting the logs/database but only after a hub reboot.
can be that the bot doesn't close the logs/database correct and keeps them in memory.
gone check this part 2night.
if you use a program like "active ports" you can see that ptokax keeps opening new ports over and over without closing them.

plop
Title:
Post by: Sudds on 28 May, 2004, 18:52:06
A few hubs im in are haveing that problem. IS there any way to solve it?Id love to know how and i would help in any way i can.
Sudds
Title:
Post by: plop on 28 May, 2004, 19:24:01
QuoteOriginally posted by Sudds
A few hubs im in are haveing that problem. IS there any way to solve it?Id love to know how and i would help in any way i can.
Sudds
fully restart ptokax and it free's up all the resources.
this problem has been sorted on the 0.3.3.0 beta.

plop