I don't know, I suppose my queries are not as optimized as I thought (even if this optimization was my leitmotiv for all the development part), or perhaps it's an apache2+php5 issue on my windows computer...
But the fact is since the database has grown (like my traffic : 6000 visitors/day and 22Mb db file), I've got more and more "maximum execution time" errors at the peak hours. I've monitored them, and it seems a lot of simultaneous queries are freezing the server and finally generates this error. The interresting point is the same queries sent a testing mysql db while the sqlite part is not responding anymore are working very well, So that's the reason why I consider to switch on a mysql solution for this website. Do you got clues concerning conversion ? 2006/2/6, Jay Sprenkle <[EMAIL PROTECTED]>: > > Hi there, > > > > I use SQLite on my website for 2 years now. I do like SQLite a lot and > > will use it for a lot of new web projects but, because I got more and > > more traffic, I consider to move this one to MySQL in order to reduce > > the over load of my computer (I host it @ home). > > How is this going to reduce load? > > sqlite = mysql - server code > > You're adding server code. More code = More load. >
