From: Stewart M. <ste...@gm...> - 2005-11-06 22:34:15
|
hi all - I've set a web app using SQLObject and mySQL (see http://www.calgarybikeroots.org), and the basic functions are working. Now I'm moving my webserver from a Pentium 3 to a Linksys NSLU2 (see http://nslu2-linux.org), and memory is at a premium. Does anyone have an idea of the relative memory footprint of sqlite vs mySql? Would I be better off switching to sqlite? Or are there even more miserly choices available? thanks, -- Stewart Midwinter st...@mi... ste...@gm... Skype, GoogleTalk, iChatAV, MSN, Yahoo: midtoad AIM:midtoad1 |
From: Oleg B. <ph...@ma...> - 2005-11-06 22:38:18
|
On Sun, Nov 06, 2005 at 03:34:07PM -0700, Stewart Midwinter wrote: > sqlite vs mySql You are compareing apples with nails. SQLite is an embedded database, MySQL is a client-server system. Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Bob I. <bo...@re...> - 2005-11-07 03:53:43
|
On Nov 6, 2005, at 2:38 PM, Oleg Broytmann wrote: > On Sun, Nov 06, 2005 at 03:34:07PM -0700, Stewart Midwinter wrote: >> sqlite vs mySql > > You are compareing apples with nails. SQLite is an embedded > database, > MySQL is a client-server system. To answer the question, SQLite almost definitely has a smaller memory footprint, but it's going to depend on how many processes you have running. If your application is architected such that it works single-process, then you're good. MySQL may eventually have a lower memory footprint if you have a lot of processes, but on such a device using a lot of processes is the wrong thing to do. -bob |