Insert 20K users in a group and try to open it in the client. See what happens (RAM and CPU monitor).
Insert 20K users in a group and try to open it in the client. See what happens (RAM and CPU monitor).
I really love your work. I hope that you will code almost everything. Like almost all the wireds, i look forward to see your next update.![]()
I hope you're not going to cache all users on startup![]()
Just use redis or memcache for caching users.
i do still wonder if this is the best solution todo, what if the emu crash?
i like your idea behind this but my server or bfly do around 30 querys /sec maxs if you got a fine database it should be no issue.
Goodluck with this project.
Last edited by vista4life; 08-07-14 at 11:46 AM.
You said that wireds are working, but when i take a look at bliep.me than there are some not working?
Like these; http://prntscr.com/3zzzwl
And you can't drag a furni from the cata to your room and buy it.
How's this emulator doing with Exploits?
Any updates?
New update!!
Ticketsystem fully working. Also the room chat button per user is fixed.
- - - Updated - - -
You don't want people to flood you every second do you? New wired is being added every week at our system. The working ones you can find in the catalogue.
- - - Updated - - -
I do agree on your point of the story, but the emulator should not be crashing anymore. This is because of @Mextur . In the case it crashes yes I do have a serious issue. But I will figure something out for this, i will probably lower the timer and make sure its being done in another thread so the users will still not be bothered by it.
- - - Updated - - -
Thanks for posting that bugg, i will put this also on my list.
- - - Updated - - -
What are you talking about... Unless you have 8000+ online which I doubt you will get 20K users within 1 minute to be imported in Groups.. And there is a simple solution for you if this is the case: Buy extra ram and a better processor.
- - - Updated - - -
There is a demo available. You can make screenshots yourself =)
Thats not my point. The client's user will stuck if you have more than 1K users in a group. It's a core feature and it won't work as it should. Rewriting support ticket systems and such should not be your focus. There are two points that require rewriting and they are it's pathfinder and the groups. The pathfinder knocks the player back if he moves too fast or if his destination is already filled. The inventory burns CPU aswell because of the way it's loading the items. It's actually the MySQL using too much CPU not the server itself. And it's all the inventory fault.
The updates you are doing will be effective for small servers only if you don't fix these points above. Copying Butterfly's pathfinder and it's inventory loading is a way to go. Groups are harder to deal with. If the group is loaded once it will load all it's users and keep them cached until it restart. Bascially we are caching all users to the memory. Some of them more than twice if they are on multiple groups. Not a way to go.
I've been looking through the server and I saw multiple times having a query and then looping over the resultset to execute another query to select stuff. The people that wrote that never heard of the JOIN clause.
I think you should focus on writing more efficient queries instead of less queries.