Jump to content

Large set of data in small chunks, SELECT inquiries only, MySQL or SQLite?


Recommended Posts

Hello,

I'm rendering a database that keeps track of the distance from every location in a map (5,000 locations - won't grow any bigger), to every location in a quick lookup table. It also keeps markers for every point in the trip in there.

 

The advatage is that it's FAST for the user now. The disadvantage is that I'm taking up about 1GB total of data. My hosting only allows 200MB per database, but gives 5GB of storage space. So, I'm thinking about using SQLite instead.

 

If I had lots of small SQLite db files (1 for each location), would there be any processing issues you can think of if people are simply SELECTing data from these files through my php scripts? There won't be any INSERTs or UPDATEs by the user.

 

Thanks for your input. :)

 

  • 2 weeks later...

That's 25 million rows for something that can be calculated fairly cheaply if you've got lat/lon for each location.  What is the typical use case?  I know much more about PostGIS, but MySQL has spatial extensions that will should do all of this for you.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.