Hard to impossible to answer. It completely depends on how you implement it.
Two extremes: You change all loading to SQL, everything stays in memory. (How rom functions today, except from flat files) It's hard to say if you would have any speed benefit here. (boot-wise) Load everything from SQL as needed, leave little in memory. This will require more work, and more disk throughput. If you have a fast disk this could work. But again, much more disk intensive. > -----Original Message----- > From: Lasher [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 04, 2002 8:24 PM > To: Tom Whiting; [email protected] > Subject: Re: OT: SQL vs MySQL > > > What type of overhead do you see using SQL vs RAM resident > pfiles/area files/etc (assuming RAM itself is plentiful)? I > wonder at what amount of players/activity on your mud you > would need something more powerful than a regular PC to make > SQL a viable option? > > ----- Original Message ----- > From: "Tom Whiting" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, December 04, 2002 2:49 PM > Subject: Re: OT: SQL vs MySQL > > > On Wednesday 04 December 2002 12:48, Greg Petty wrote: > How does MySQL compare to SQL? Are they > > interchangeable? I have already implemented a Linux file/print and > > working on adding an Apache webserver onto my network, and > I'd like to > > add a MySQL db server if at all possible. > MySQL is simply a version of the SQL language as far as I > understand it. You've got a million and one versions (well > maybe not ThAT many, but it's a decent #) of SQL based > languages (M$SQL, PostGresql, MySQL are the top three the > come to my mind). Adding a MySQL server is actually easily > done, if you've got a redhat system, find the rpm's and > install them. otherwise, head on over to www.mysql.com, dig > around there a bit (you might be better off doing a search on > freshmeat for a direct link). As far as MySQL vs files, well, > that's just my personal preference. Eventually, I'll have the > majority of the structures saved/loaded in sql, in order to > deal with web based playing as WELL as client based (that > one's still a LONG way down the road though). Editing users > in this type of a database completely frees up everything > though. No need for pload,just pset player (blah, value), and > if it is a legal area to be set it's done, whether they're on > or off line. It's definitely got its advantages to flat files. > > > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom > > > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom >
