[gameprogrammer] Re: sqlite example program
- From: Robbert de Groot <zekaric@xxxxxxxx>
- To: gameprogrammer@xxxxxxxxxxxxx
- Date: Sat, 22 May 2010 21:42:20 -0700 (PDT)
No I'm well aware of file caching. But if you are accessing a file that isn't
in the cache then file caching is meaningless. I'm just saying that DB access
is not necessarily slow. So don't rule it out if that is your only fear.
Robbert de Groot
--- On Sat, 5/22/10, Ethan Grammatikidis <eekee57@xxxxxxxxxxx> wrote:
>
> On 22 May 2010, at 22:32, Robbert de Groot wrote:
> >
> > The guys who code SQL server do a lot to eek out any
> performance they can. They 'cache' a lot in
> memory. If you are talking to a server somewhere else
> on the net then your local computer will do some caching so
> that only the first fetch is slow but subsequent ones may
> not be. Other big database offerings will do similar
> tricks. Even though the database is on the hard drive,
> or possibly over a network, it's quite possible that a lot
> of the data is copied into memory on your machine. You
> can't beat that if your alternative solution is to find and
> read a file.
>
> Um, I may be reading it wrong but it sounds like you've
> never heard of file caching. *ducks* ^^; I haven't done much
> with network file systems, but I imagine it's normally done.
> I can't remember what I read about it the last time I messed
> with nfs, I think you could choose whether to allow the
> client to cache.
>
> I guess a database may be able to cache 'smarter' than a
> filesystem, depending what you're doing with it, but for
> simple matters I still don't see how a database can be
> faster. Anyway, I'm rather subverting the thread. I'd better
> stop now.
>
> --Simplicity does not precede complexity, but follows it.
> -- Alan Perlis
>
>
> ---------------------
> To unsubscribe go to http://gameprogrammer.com/mailinglist.html
>
>
>
---------------------
To unsubscribe go to http://gameprogrammer.com/mailinglist.html
Other related posts:
