Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fatalmind
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
fatalmind
12y ago
I've given this talk on Saturday in Moscow again and it was video taped there. Organizers told me they'll publish the English original as well as the Russian voice over version. I'm keen for the second one ;) I keep you poste
2.
▲
by
fatalmind
12y ago
X-comment so you get it too: Quoting from http://Use-The-Index-Luke.com/ (the main page): Use The Index, Luke is the free web-edition of SQL Performance Explained. If you like this site, consider getting the book. Also have
3.
▲
by
fatalmind
12y ago
Quoting from http://Use-The-Index-Luke.com/ (the main page): Use The Index, Luke is the free web-edition of SQL Performance Explained. If you like this site, consider getting the book. Also have a look at the shop for other
4.
▲
by
fatalmind
13y ago
That 100GB+ guide has re-appeared at a new URL: http://blog.mongodb.org/post/62899600960/scaling-advice-from-mongohq
5.
▲
by
fatalmind
13y ago
The MsSQL locking problems is just because snapshot isolation is disabled per default: http://use-the-index-luke.com/blog/2011-06-24/dear-database-...
6.
▲
by
fatalmind
13y ago
Seems like. That's also what this comment on Reddit says: http://www.reddit.com/r/programming/comments/1niheb/mongodb_...
7.
▲
by
fatalmind
13y ago
here you go: http://use-the-index-luke.com/sql/join/hash-join-partial-obj... It's really a PIA. Recently, I've learned about http://jooq.org/ — not having checked in detail yet, it might
8.
▲
Myth: Select * is Bad
(use-the-index-luke.com)
87 points
by
fatalmind
13y ago
|
67 comments
9.
▲
What every developer should know about SQL performance
(use-the-index-luke.com)
1 points
by
fatalmind
13y ago
|
0 comments
10.
▲
Use The Index, Luke: SQL performance guide now with online examples on SQLFiddle
(use-the-index-luke.com)
2 points
by
fatalmind
13y ago
|
0 comments
11.
▲
About SQL Query Hints: Not all hints are born equally
(use-the-index-luke.com)
1 points
by
fatalmind
13y ago
|
0 comments
12.
▲
There are only two hard problems in web design: Internet Explorer and Fonts.
(twitter.com)
2 points
by
fatalmind
13y ago
|
0 comments
13.
▲
Indexes: The neglected performance all-rounder
(use-the-index-luke.com)
2 points
by
fatalmind
13y ago
|
0 comments
14.
▲
Afraid of SSD?
(use-the-index-luke.com)
1 points
by
fatalmind
13y ago
|
1 comments
15.
▲
A URL to toss at your SQL devs
(use-the-index-luke.com)
1 points
by
fatalmind
13y ago
|
0 comments
16.
▲
The two top performance problems caused by ORM tools
(use-the-index-luke.com)
5 points
by
fatalmind
13y ago
|
1 comments
17.
▲
The second power of SQL indexes: Clustering Data
(use-the-index-luke.com)
3 points
by
fatalmind
13y ago
|
0 comments
18.
▲
Response Time, Throughput and Horizontal Scalability
(use-the-index-luke.com)
2 points
by
fatalmind
13y ago
|
0 comments
19.
▲
Database indexing is a development task—it needs the same care as schema design
(use-the-index-luke.com)
7 points
by
fatalmind
13y ago
|
0 comments
20.
▲
FOSDEM Impressions
(use-the-index-luke.com)
1 points
by
fatalmind
14y ago
|
0 comments
21.
▲
by
fatalmind
14y ago
Other formats (PDF and paperback) are available on a commercial basis: http://sql-performance-explained.com/
22.
▲
SQL Indexing and Tuning e-Book
(use-the-index-luke.com)
130 points
by
fatalmind
14y ago
|
11 comments
23.
▲
Expert, competent, or greenhorn? Test your SQL performance skills in 3 minutes
(use-the-index-luke.com)
1 points
by
fatalmind
14y ago
|
0 comments
24.
▲
Adding hardware won't fix response time problems.
(use-the-index-luke.com)
1 points
by
fatalmind
14y ago
|
0 comments
25.
▲
Indexing many columns individually won't give you best database performance
(use-the-index-luke.com)
1 points
by
fatalmind
14y ago
|
0 comments
26.
▲
A quiz that teaches you how to avoid the most common SQL performance issues
(use-the-index-luke.com)
1 points
by
fatalmind
14y ago
|
0 comments
27.
▲
by
fatalmind
14y ago
Besides your points, we must also consider that MySQL does neither support hash joins nor sort/merge join. MySQL it just not very good at joining. Nevertheless, a MySQL join should never be slower than the N+1 select approach.
28.
▲
Get to know your ORM and take control of joins.
(use-the-index-luke.com)
40 points
by
fatalmind
14y ago
|
23 comments
29.
▲
Stop worrying and learn to use the index
(use-the-index-luke.com)
2 points
by
fatalmind
14y ago
|
0 comments
30.
▲
A visual explanation why SQL's LIKE is slow
(use-the-index-luke.com)
1 points
by
fatalmind
14y ago
|
0 comments
More ›