171 reputation
5
bio website aws.amazon.com/training
location São Paulo, Brazil
age 27
visits member for 2 years, 4 months
seen Sep 11 '13 at 5:29

Mechatronics Engineer from Poli/USP (University of São Paulo, Brazil) and General Engineer from École Centrale de Lille (Lille, France).

Passionate about software programming since a kid. Interested in algorithms, concurrency, scalability, big data, object oriented and functional programming.

Currently working as a Technical Trainer at Amazon Web Services. Learn more at https://aws.amazon.com/training/.

We're hiring! See https://aws.amazon.com/careers/


  • AWS Certified Solutions Architect - Associate Level
  • AWS Certified SysOps Administrator - Associate Level
  • AWS Certified Developer - Associate Level

Sep
9
comment Merging Large Database Tables Quickly
It would be useful if you gave more details about your data and setup. Could you please add to your question the output of show create table X, where X would be each of your three tables? Also, where are you running these databases? I'd guess on AWS because of the tag -- if this is the case, is this RDS, or did you install MySQL on an instance on EC2 by yourself?
Apr
10
awarded  Scholar
Apr
10
accepted How to make MySQL 5.1 connection ignore kills?
Apr
10
revised How expensive are SELECT FROM LIKE statements from a design perspective?
added 509 characters in body
Apr
10
revised How expensive are SELECT FROM LIKE statements from a design perspective?
added 179 characters in body
Apr
10
revised How expensive are SELECT FROM LIKE statements from a design perspective?
added 1 characters in body
Apr
10
answered How expensive are SELECT FROM LIKE statements from a design perspective?
Apr
10
comment How expensive are SELECT FROM LIKE statements from a design perspective?
let us continue this discussion in chat
Apr
10
comment How expensive are SELECT FROM LIKE statements from a design perspective?
Also: what exactly is your "criteria"? Is it really free text? Could you make it somehow a bit more structured? FYI, the first of your queries (like 'xxx%') would run fast if the column is the last part of the used key, while the others (like '%xxx' or like '%xxx%') would run slow (in the worst situation -- without more conditions, as in your examples -- you would have a full table scan, which would likely kill your server).
Apr
10
comment How expensive are SELECT FROM LIKE statements from a design perspective?
What kind of content are you talking about? How are you using this content? What exactly do you mean by small (in bytes)? Is your content mostly read-only, or is it frequently updated?
Apr
10
comment How expensive are SELECT FROM LIKE statements from a design perspective?
Would you care to explain a bit more about your original situation? What exactly is your problem? Why must you reduce the number of files? I ask because I might have a similar situation, but mine is totally under control. I have a single, small server serving about 15M requests per day randomly distributed among about 2.5M small static files (mainly images, most around 0.6kb - 2.5kb, some a little bigger), and I can assure you that the server load is very, very low: it could handle a lot more.
Apr
8
awarded  Teacher
Apr
8
awarded  Student
Apr
7
awarded  Editor
Apr
7
revised How to make MySQL 5.1 connection ignore kills?
added 191 characters in body
Apr
7
answered How to make MySQL 5.1 connection ignore kills?
Apr
7
asked How to make MySQL 5.1 connection ignore kills?
Apr
7
awarded  Autobiographer