Complete.Org: Mailing Lists: Archives: freeciv-dev: May 2003:
[Freeciv-Dev] Re: client/server authentication (PR#1767)
Home

[Freeciv-Dev] Re: client/server authentication (PR#1767)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: kaufman@xxxxxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: client/server authentication (PR#1767)
From: "Paul Zastoupil" <paul@xxxxxxxxxxxxx>
Date: Wed, 7 May 2003 11:01:34 -0700
Reply-to: rt@xxxxxxxxxxxxxx

On Wed, May 07, 2003 at 07:54:20AM -0700, Mike Kaufman wrote:
> On Wed, May 07, 2003 at 06:32:57AM -0700, Raimar Falke wrote:
<snip>
> > I'm for waiting. It is easier to program. If there however are systems
> > which need 5s to retrieve the data and people want to use these as
> > user-db I will change my mind.
> 
> After I wrote this last night I thought about it for a while. I was on
> crack. I just did a bit of googling, and I see that databases ought to be
> faster (at least for the size of databases we're talking about --- I don't
> see our pubserver database going much beyond 20000 entries do you? ;) than
> the times we're worried about. There's also no reason to fork processes, we
> can put our db API right in the lib. Or if we do fork, we can put our
> timers in the lib and return after a suitable time.

FWIW, a "select * from players" on the current pubserver database:
8366 rows in set (0.20 sec)
On a single player (after adding an index on name since we'll be using that):
1 row in set (0.00 sec)

This is all running on db.freeciv.org (which is that Ultra2).  That
whole database is probably cached (I did buy extra RAM).  So these
numbers may mean nothing regarding your average machine.

So with this in mind, I hunted down a linux mysql server we use here for EQ
logging.  I did a select * on a table with 2 columns, ID and name.
34489 rows in set (0.20 sec)
1 row in set (0.06 sec)

I think 5 seconds would be a very worst case scenario.
-- 
Paul Zastoupil



[Prev in Thread] Current Thread [Next in Thread]