Upcoming changes

[Smedy]

Maybe naez or whoever the fuck this is should work on his teeth issue and stop holding rogean from putting these ones and zeroes in the correct places

We all know about that teeth issue dog and i'm willing to donate @your paypal if you can provide dentist visit receipt

[Splorf22]

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

Anything that locks up the process waiting for a response from a different service, even if it's just an ACK from a database insert, is a bottleneck. What happens if the database query gets lock queued (because that does happen from time to time with 1k users online). There's a reason removing the bulk of on-demand SQL Queries from zoneprocess improved our stability tremendously.

You're thinking strictly from a database model point of view. What you need to consider is everything else that goes on including the code in the zone process itself handling all the database code, the transport code, and then the WAITING it does. You shouldn't have to fucking WAIT for a database to go "Herr ok I inserted it" before resuming code execution on an UPDATE/INSERT. (And yes, you still get the same problem with INSERT DELAYED, although only slightly improved).

100% agree that a database call is way more of an issue on a realtime game server than a webpage. I guess if I had to do it I would

a) Load all the info out of the database on server start/player login
b) Just have a simple write to 'the big logfile' (just copy the structs directly out of memory) so very fast
c) Have another process/thread which stuffs things into the database (If you want to make any sort of queries you'll have to either use a database or reinvent the wheel)

But I wouldn't be super happy with this, because I'd be giving up reliability. From what little I remember there is no way for the server to confirm that the logfile was actually flushed to disk before confirming the trade with the user AFAIK without using the very slow fsync call, so we aren't exactly talking banking level reliability here.

Kind of curious exactly what you did now [You must be logged in to view images. Log in or Register.]

[Rogean]

Originally Posted by Splorf22 [You must be logged in to view images. Log in or Register.]

c) Have another process/thread which stuffs things into the database (If you want to make any sort of queries you'll have to either use a database or reinvent the wheel)

/clap

[Colgate]

Originally Posted by Colgate [You must be logged in to view images. Log in or Register.]

can we get a confirmation on what color said text will be?

[GODPARTICLE]

I never claimed it was the most efficient implementation, however it is a practical way to accomplish a realtime updateable system for when you think of new phrases to use with realistically negligible overhead besides nitpicking

[Obwin]

People wonder why "one line of code" takes a long time to put in. If you are so good at it go make your own server and shit it up with crappy code.

I have no stake on r1999 and I am just a lurker here but I love classic EQ and will be back if some of the changes bring back people. FWIW I'd love to see samwise get his way but I know how much work this takes.

Just remember these guys that support this project, for FREE, in there personal time have a skill that is billable in the hundreds to thousands of dollars an hour. To all you college grads that think you are gods gift to coding, go get a real job, with real deadlines, work 60-80 hours a week for some BS corporation that can never give good business requirements. Recode your shit 80 times because users don't understand how to give requirements, get yelled at for not reading minds and not delivering perfect products in ridiculous timeframes. THEN spend all your remaining free time supporting a sever full of whiney know it alls, sitting that in their basement/dorm room smoking weed all day blasting you / each other with racial slurs and homophobic cutdowns in response to every well thought out post/suggestion.

It's no wonder not much gets done around here. Can't say I'd be very motivated to help either. My dream of finding a classic MMO experience that isn't shit up by a community of assholes is slowly dying. Try to log in and enjoy server for what it is, end up listening to a dick conversation in /ooc for 45 minutes. Immersion ruined.

<waits for racially charged/homophobic response>

[Pudge]

Thank you Rogean!
For the PvP text [You must be logged in to view images. Log in or Register.]

Edit: I see the above poster was thinking the same grateful thoughts as I was. And Rogean those pics are badass. I see you even have a tab for items dropped on the ground! Haha

[GODPARTICLE]

Trips to the database are extremely fast, the bottlenecks are in the queries which is why they pay people the big bucks to optimize them. In the converted relational algebra to get a random saying, all you have is a single projection operation which is probably passed into a mersenne twister (or whatever random generator mysql uses), no sigmas, intersections, unions, cartesian products, or tuple joins; which is where inefficiency comes into play (even moreso with myisam). Pretty much all you're waiting for is the rotational delay of the hard drive and a single block transfer time. If we were really worried about database workload I imagine the project would have switched to something more robust like postgresql ages ago.

[reddi lol]

Originally Posted by GODPARTICLE [You must be logged in to view images. Log in or Register.]

I never claimed it was the most efficient implementation

Obviously you degree was from Devry institute of technology cus ***** u dum

[Obwin]

Originally Posted by GODPARTICLE [You must be logged in to view images. Log in or Register.]

Trips to the database are extremely fast, the bottlenecks are in the queries which is why they pay people the big bucks to optimize them. In the converted relational algebra to get a random saying, all you have is a single projection operation which is probably passed into a mersenne twister (or whatever random generator mysql uses), no sigmas, intersections, unions, cartesian products, or tuple joins; which is where inefficiency comes into play (even moreso with myisam). Pretty much all you're waiting for is the rotational delay of the hard drive and a single block transfer time.

Has nothing to do with discussion. Copied from textbook.