yeppa more as 30 ppl you get probs but coly m8 that was for sure with lower server specs that time today if you rent a dedi server it have higher specs and than it make no problems as i said minimum for that way is rly 2 Ghz Cpu and minimum 1 Gig Ram or better 2 Gig. And Emerald it looks like you know much or you think you do *hehe
If you will not believe me than believe Coly he know deffently what he is talking about.
And the part with sql lol all what is needed with Var´s is also possible with txt files and not slower in my eyes its faster and also what coly say with server sql requests if you make to much in sql and have it one same system as the server you have also only trouble. For ppl that have not the Possibility to rent 2 or 3 diffrent servers and make all at one server better use for vars txt files (you see it nice in woool files there nearly all vars safed in txt files and there you have rly no lagging system.
anyways i would be interested to know emeralld if you have test it out with txt and sql what time does it lag and what time not Coly and Me and much other have made it. Idabiga do nearly all with Sql i dunno what system he run but i am sure he use a 2nd host for sql same like zedina do and some others
You really are sparse with your actual reading and understanding of what I said arn't you, but then again myabe that has to do with the lack of lateral thinking on your part. As you really do tend to speak before thinking.
A two server system, one running the server files and the other running the sql server is not going to cause any lag at all. Especially if they are on the same core network as each other, but as I said if running everything from one server and you only have a cpu of 2ghz and 2gb memory running a hefty quest script system with 30+ players on the server. You are going to noice lag, whether it be from the scripts that are running in the background or the other features that are running within game.
Yes I have built both sql & .txt scripts and also combined both into one quest system. A high end of variables works far quicker in a sql system, than what it does in a .txt script. I also build sql databases as a day to day job and I fully understand that a system that is under par to the database will cause issues with it.
DB wait errors are caused by scripts reading into the sql and refrencing the information to quick and cause's timeouts within the db, this is why I find using both .txt and sql at the same time a far better option for creating a far complex script.
but all that have read till here hey you got all you need some postings before :P