Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
spudlyo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
63 ms
·
751.
▲
by
spudlyo
14y ago
Hopefully you don't have an auto-increment int (2^31) as a PK, or you'll be worrying sooner than you think.
752.
▲
by
spudlyo
14y ago
Ya, recovery time is a big deal. It's like the difference between ext2 and ext3. With ext2 a crash is gonna require a lengthy and painful fsck, especially if your table/filesystem is large. A journaled filesystem is a lot like a database
753.
▲
by
spudlyo
14y ago
I saw chunk load time increase from 1m40s to around an hour per million inserts. Your insert performance falls off a cliff when a majority of the index pages for the table no longer fit into the innodb buffer pool. After that happens, th
754.
▲
by
spudlyo
14y ago
And if you do, for God's sake don't run them on EBS volumes. If you don't know by now that EBS performance is highly variable, you really haven't been paying attention.
755.
▲
by
spudlyo
14y ago
It's also great that pv supports rate limiting, so you can choose if you want to saturate your network when you use it with netcat.
756.
▲
by
spudlyo
14y ago
Linux filesystems like ext(2|3|4) don't zero the contents of the data blocks, and you can use tools to recover the data.
757.
▲
by
spudlyo
14y ago
... and then destroy them with robotic spur-winged plovers.
758.
▲
by
spudlyo
14y ago
I felt that this was was an interesting read. http://www.reddit.com/r/IAmA/comments/otl8z/iama_diagnosed_p...
759.
▲
by
spudlyo
14y ago
Your MySQL example isn't exactly relevant. It was in 2007, yet you said "MySQL still tanks at 8 cores". Furthermore it was on FreeBSD, with a flawed libpthread. In terms of "real" workloads, I'm not going to bother getting into it, as thi
760.
▲
by
spudlyo
14y ago
No, it's not. The referenced article is talking about Postgres 9.2devel. Version 9.2 isn't out yet, and even if it was, it still wouldn't be true due to the clause "and has done so for a few years". The lock manager bottlenecks that stopp
761.
▲
by
spudlyo
14y ago
The key is that PostgreSQL 9.2 will be able to handle a 64 core workload, but current released versions of PG do not. The fact is current versions of PG are unable to use more than 60% CPU on a 24 core machine. Do you know anyone who use
762.
▲
by
spudlyo
14y ago
Postgresql will scale to 32 cores with a real workload, and has done so for a few years. Mysql performance still tanks at 8 cores. Both of those statements are not accurate, but hey, what's it matter? Without benchmarks we're both talki
763.
▲
by
spudlyo
14y ago
This is InnoDB's sweet spot really -- a mostly read-only in memory data set where the lookups are done primarily by PK. MySQL 5.5 can scale this kind of workload to 32 cores. I'm pretty sure given this kind of workload MySQL will outperfor
764.
▲
by
spudlyo
14y ago
We were excited to try a NoSQL db, having spent too many years using MySQL in ways that the designers of relational databases never imagined. ... Given that we had experience with MySQL and knew it was adequate for our needs, it was hard
765.
▲
by
spudlyo
14y ago
Normalize 'til it hurts, denormalize 'til it works.
766.
▲
by
spudlyo
15y ago
Agreed. I thought the parent was ill served by editing the post and moderating the language, which for me more accurately described how I felt about the article and situation.
767.
▲
by
spudlyo
15y ago
Obsequious omphaloskepsis.
768.
▲
by
spudlyo
15y ago
You might be right. In my testing, mdworker and friends behave like you'd want them to, I don't see them polluting the cache on my Lion machine. Haven't tried time machine yet. EDIT: I can't get either spotlight or time machine to show an
769.
▲
by
spudlyo
15y ago
The notion that disk cache is so ungodly important that the OS will SWAP MY APPLICATIONS OUT TO DISK PRESERVE IT boggles my mind a bit. Users of desktop systems clearly don't like this behavior, in fact they'll do crazy things like purgin
770.
▲
by
spudlyo
15y ago
What really needs to happen is that Spotlight and Time Machine need to use direct i/o (F_NOCACHE) when they read data from the filesystem, this way they won't pollute the disk cache with their reads and OSX won't swap out a bunch of pages i
771.
▲
by
spudlyo
15y ago
I don't recognize any of his symptoms anyway, and my OS X computers get pretty RAM-heavy use, with almost always a linux VM open, XCode, Safari with ~10 tabs, iTunes with a few thousand songs, etc. I think you missed a key ingredient to t
772.
▲
A brief update on NUMA and MySQL
(blog.jcole.us)
41 points
by
spudlyo
15y ago
|
4 comments
773.
▲
by
spudlyo
15y ago
One interesting improvement relates to NUMA node allocations. I think the reasoning is that if you touch all the memory in the buffer pool after you allocate it, you're more likely to get a balanced node allocation than if you let MySQL org
774.
▲
by
spudlyo
15y ago
The master's tools will never dismantle the master's house. --Audre Lorde
775.
▲
Seattle vs. Silicon Valley
(venturebeat.com)
1 points
by
spudlyo
15y ago
|
0 comments
776.
▲
by
spudlyo
15y ago
It makes me feel a little embarrassed for HN actually. This article might be a revelation for the noobs on the Linux subreddit, but I'd expect the HN crowd to find it pretty pedestrian. Not only that, but in some cases it is flat-out wrong
777.
▲
by
spudlyo
15y ago
You'd be surprised how good and feature rich plain ole top actually is. My guess is you rarely deviate from the default options. I made a video which shows how you can get top to show you some pretty interesting stuff. http://www.youtube
778.
▲
by
spudlyo
15y ago
I've heard some of my friends in the gaming industry talk about a sea change towards free-to-play games, beyond the MMO genre. Monetization schemes include advertising, access to better/faster servers, in-game purchases of items/adornments
779.
▲
by
spudlyo
15y ago
I know you're joking, but it's not the fault of emacs that the de facto PC keyboard layout has the control key in a stupid position. If you've been a heavy user of emacs (or any tool that requires a lot of control key sequences) for any amo
780.
▲
by
spudlyo
15y ago
The not-so-nice disadvantage that your cold spare can't actually do any work (like serve read traffic) and that if your application itself corrupts data DRBD will dutifully mirror that corruption. Hopefully the spare can still perform well
More ›