Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's difficult to say much about this without knowing anything about the particulars of the data you are loading. Does MySQL have to update indexes in the table? Is everything already sorted properly? How many columns are there, and are you performing any CPU-intensive operations in your <code>LOAD DATA INFILE</code> statement (e.g. replacing parts of strings)? Is old data deleted after a certain period of time, or should all data be retained for the life span of your application?</p> <p>Having said that, it sounds like a single Micro instance will probably have trouble dealing with this. Importing the data should be OK provided you back up the instance with plenty of EBS storage (maybe in a RAID configuration), but if that single instance will also be responsible for running user queries on such a large data set, that's probably not going to run very smoothly. At best you'll end up with a few seconds' latency for user requests when the import script is running. Depending on your application, that may or may not be acceptable. </p> <p>If you are going to run expensive queries on your data, I can say right now that that is not going to work very well on a single Micro instance :) You could scale up to a larger instance or depending on your needs, you may also want to consider using SimpleDB or a similar NoSQL solution instead (though that would take more code in your import script, because you'll have to do batch puts of at most 25 items per batch). </p> <p>But these are just some general thoughts. And AWS actually provides new users with a free usage tier, which lets you run an EC2 Micro instance continuously for a full year without having to pay a dime, so why not sign up for an account and run your own tests? More details <a href="http://aws.amazon.com/free/" rel="nofollow">here</a>. <a href="http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/concepts_micro_instances.html" rel="nofollow">Here</a>'s some more general information on how micro instances work and what applications they would be suitable for.</p>
    singulars
    1. This table or related slice is empty.
    1. POEC2 server, Would a Micro Instance be enough?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDaan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEC2 server, Would a Micro Instance be enough?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBefore import I truncate the table, then on import it just takes the data from the file and puts it in the database. The table in the database contains 6 column (mediumint,varchar(26),smallint,smallint,int,smallint). As for Keys there is a primary on the id (mediumint) index on the int, and a unique on a join of the 2 smallints. As for queries they will specifically search via the primary key, unique key, or via the index key. Each query will generally return a single match, I have a few queries that will return 1-1000results though the index key, and some are results based on calculations.
      singulars
      1. PO
      1. USSteven10172
    2. COWhen the queries happen I would like them to be almost instant, and every page view will have some kind of query, usually a simple get by the id which is a primary key.
      singulars
      1. PO
      1. USSteven10172
    3. COHmm. It'd probably be best to import into a separate table to prevent users from being unable to access any data at all after truncation, while you're still loading new data. I think the problem for you is going to be that MySQL can't build these indexes quickly enough on a Micro instance - maybe if everything is already sorted and if there are no unique key issues, but still, that's going to be a heavy hit to a micro instance.
      singulars
      1. PO
      1. USDaan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload