11–20 of 39 posts
https://www.mapbox.com/guides/an-open-platform/#storing-tile...
you can have sqlite databases that are gigs in size and perform great.
I was fooled by the name for a long time. "SQLite? That's what you use to store 160 phone book entries or something." How wrong I was.
I'm using it for the data catalog for one of my projects (a Linux backup tool) which I've grown to something like 20GB, and storing the metadata catalog for 40 systems and about 30 backup sets for each one. So far the main issues I've been having is I have a lot of complex joins, and it doesn't seem to want to use appropriate indexes all the time. If I'm joining 2 tables on an indexed field, it is ok, but as soon as…
SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. I am curious to know how many people here solely use SQLite to power the back-end of their web application(s), especially when the page states, " SQLite does not compete with client/server databases. "…
Earlier quoted context omitted.
I'm using WebSQL / Sqlite to store TV show data on the user's system. works like a charm, databases regularly grow to 10+mb, never had a problem with crashes, speed or anything like it. Plus, everything runs locally Now I really hope that Spartan can implement WebSQL as well...
I look forward to using SQLite again. In 2010ish I used it for an airport and aircraft database to be installed with our iOS app for 'find near you' feature. lookup performance was perfect. but did have some performance snags on application start, a server call retrieved any DB records needing to be updated. I found SQLite update statements were slow (10mb DB of 10,000 records, less than 100 updates took 30s on first…
How does SQLite handle replication? Can I have 10 app server nodes reading from one SQLite DB? NFS?
SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. I am curious to know how many people here solely use SQLite to power the back-end of their web application(s), especially when the page states, " SQLite does not compete with client/server databases. "…
Well, we've tried distributing applications that needed to share a DB backend. We tried a MS Access backend first, but it stopped working after about 5 people were using it. Then we migrated to SQLite, it handled well up to near 50 people, then its over-restrictive locking become a problem. Luckly by that time we got hold of an Postgres server.
Low to medium traffic websites don't usualy have much more than 10 working threads, so yes, I've used a lousely similar setup, and it worked. It'll depend on how much time is spent on DB access vs. local processing, and how fast the DB is accessed by those servers, so YMMV.
SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. I am curious to know how many people here solely use SQLite to power the back-end of their web application(s), especially when the page states, " SQLite does not compete with client/server databases. "…
If you however cause writes when people open pages, look at content. Anything from hit counters to tracking behaviour. Then SQLite suddenly starts to scale pretty badly.
The same goes with how your processing works. Multiple processes that may all at some point cause writes? This is bad. Threads inside a process? That works.
I was fooled by the name for a long time. "SQLite? That's what you use to store 160 phone book entries or something." How wrong I was.
I'm using WebSQL / Sqlite to store TV show data on the user's system. works like a charm, databases regularly grow to 10+mb, never had a problem with crashes, speed or anything like it. Plus, everything runs locally Now I really hope that Spartan can implement WebSQL as well...
Sounds unlikely given that the standard was superseded by IndexedDB.
http://www.html5rocks.com/en/tutorials/webdatabase/websql-in...
Most browsers just use SQLite to back IndexedDB, though.
SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. I am curious to know how many people here solely use SQLite to power the back-end of their web application(s), especially when the page states, " SQLite does not compete with client/server databases. "…
However, if you're running your website on Apache, on a single webserver, then there's really only ONE client for your database, in which case SQLite works great, even if there's a heck of a lot of load.
SQLite is fundamentally a C library talking to a binary file format, so it's orders of magnitude faster than making a network connection to a client and then issuing SQL.
I've run medium-sized websites on an MVC framework talking to SQLite MANY times, and it works great.
How does SQLite handle replication? Can I have 10 app server nodes reading from one SQLite DB? NFS?
I'm not sure if SQLite writes over NFS work, I wouldn't trust it. Previously I have done SQLite replication by simply rsyncing the database to application servers at certain times.