Okay, well after a few remarks from Tom, Ian, and a few other friends. The same remark had come up :
"There will surely be a game that will crash the server"
That remark is very very true, but once I do some research, I am sure that there will be some sort of a package that let's me assign a limited amount of ram to each person. Now, I must begin my search, also if possible anyone who would like to, please search and find a package.
Keep posted for regular updates!
ID:86889
 Dec 4 2009, 11:23 am
|
|
|
Dec 4 2009, 12:46 pm
|
|
Neblim
 |
A crash is usually a result from a memory leak which snags godly amount of memory at a uncontrollable rate for the computer it is on. This has nothing to do with the player, but good ol' OOP programming and how Byond handles itself.
|
Qubic people have went over you with this on the forums why your BYONDserver idea is a flawed one. There is only money to be lost.
| |
Neblim wrote:
memory leak (...) OOP programming and how Byond handles itself. Memory leaks aren't directly related to object-oriented programming in any reasonable way. How you come to that conclusion is past me. As for how BYOND handles memory allocation, it is possible to hog intense amounts in any programming language. BYOND actually does a rather neat job at preventing beginning programmers from screwing up. Imagine the rippers trying their skill on C/C+++ malloc. The sheer thought that they'd have to keep track of and free memory at a later point in time would be prone to some interesting results. | |
Qubic wrote:
after a few remarks from Tom, Ian, and a few other friends Would you happen to be allowed to share these remarks? I'm curious as to what Tom and Ian pointed out ;) | |
OOP was the wrong term, I'm sorry. However, you can only pile so much "garbage" in Byond's little "garbage collector" before things start to really stink. How exactly Byond handles its allocation and deallocation I haven't researched too far in depth, but I do know it is possible for a game to screw up with this system. Sirogana Legend (sp?) once done this and it was obvious that there were some issues with it.
Bad programming can still screw things up bad. Look, game servers for different games crash from time to time. The point is, they will crash, and if one goes, likely they will all go, depending on the issue. If it's a memory issue, they all will. Imagine hosting enough games to fill 1000 players. That's actually kind of scary. Yes, Byond does do a nice job at this (compared to many many languages for beginners), but so does Java. Does Java screw up once in awhile? Yes. It's just inevitable.. No programming language has created the "silver bullet", so to speak, yet. Again, I'm not putting this idea down, but the likelyhood you're going to need more than 1 server on a dedicated line is quite high. | |
Neblim wrote:
you can only pile so much "garbage" in Byond's little "garbage collector" before things start to really stink. I never stated otherwise, but that very statement is true for any programming language. Neblim wrote: Bad programming can still screw things up bad. Again, this is true for every programming language. Neblim wrote: you're going to need more than 1 server on a dedicated line is quite high. If I recall properly, I stated that on the previous blog. | |