HNHacker News
TopNewBestAskShowJobs

AaronBBrown

330 karma · joined May 4, 2012

submissionscomments
AaronBBrown··on PostgreSQL Rising
Are you suggesting that there isn't "serious commercial support" available for MySQL? Oracle, Percona, SkySQL, and a number of other businesses provide high quality support for MySQL installations.
AaronBBrown··on PostgreSQL Rising
As I mentioned, I do like PostgreSQL for its consistency and I want to like it even more. Cascading replication looks interesting - does it support the topology that I mention where the master has a subset of the from the slaves and the slaves can be written to? The documentation is difficult to decipher and lacks examples.

I don't mean this to be MySQL vs PostgreSQL, but MySQL has had these features for over 10 years and the kinks are already worked out. It's one of the main reasons for the success of the platform. My X,Y, and Z list has been unchanging for 5 years when I first started maintaining a medium sized Slony-I cluster that required a complete rebuild and several hours of downtime every few months. I suspect that's true of most operations-focused folks who have maintained PostgreSQL clusters. Devs love it, DBAs love it, but it is Operations that holds the keys to the kingdom.

AaronBBrown··on PostgreSQL Rising
Objective citation, please?
AaronBBrown··on PostgreSQL Rising
I just watched a 10 minute video whereby nearly all the issues pointed out can be solved with one line in my.cnf or dynamically by setting SET GLOBAL server_sql_mode=TRADITIONAL. Yeah the default is no good. Learn your RDBMS and the problem goes away. Watching him point and click and move windows around also made it very difficult to follow.

PostgreSQL is an awesome RDBMS, but adoption will never eclipse MySQL until they have a scalable replication model that allows tiered replication, multi-master replication, writable slaves (very useful for reporting boxes), and the ability to purge data on a master without purging it on the slave. That, and the ability to reliably upgrade your binary without performing a massively time-consuming dump and reloading. Replication and upgradability is everything when you are in operations, which are things many (not all) developers do not consider.

AaronBBrown··on Why the days are numbered for Hadoop as we know it
Flume is only related to MapReduce in that it is able to write to HDFS. All Flume is is a transport mechanism to send log-like data from one place to another. It can be made fancy by adding decorators to manipulate the data along the way, but at its core, it just moves bytes around. Unfortunately, at this stage, it's highly unreliable with its fault tolerant design causing more problems than it solves. Hopefully FlumeNG will improve upon this. I speak as someone who runs Flume in production and has to deal with it constantly failing on me, usually silently.

It's a great technology, but it just isn't there yet.

AaronBBrown··on Why the days are numbered for Hadoop as we know it
Can HN just ban gigaom articles? Have they ever written a single technically interesting or accurate article in their entire existence? It's all just spin.
AaronBBrown··on Dr. Dobb's 2012 Salary Survey
Apparently, $11,000
AaronBBrown··on Ex-Facebookers launch MemSQL (YC W11) to make your database fly
Another key point is that temporary tables are horrible for concurrency. Obviously only one session can access them, but more importantly, they end up causing a great deal of disk activity. At the end of every session, the table is physically dropped. In ext3, this can take quite a while for large tables (not so bad in filesystems like xfs). It also can cause substantial stalls in InnoDB as the buffer pool is scanned for matching pages and are flushed out. Percona Server has innodb_lazy_drop_table to mitigate this issue to some degree, but dropping tables is still always an expensive operation. This is mostly a concern for OLTP, not necessarily OLAP servers.
AaronBBrown··on Ex-Facebookers launch MemSQL (YC W11) to make your database fly
You are clearly not talking about MySQL. CREATE TEMPORARY TABLE simply creates a physical table on disk that is destroyed at the end of the session, which can be created with any storage engine. Explicit temporary tables are handled just like "regular" tables and is dependent upon the storage engine (w/ MyISAM, indexes are stored in the key buffer, InnoDB keeps both recently accessed data and indexes in the InnoDB buffer pool).

KEY and INDEX are literally the exact same thing and are just there to support different syntaxes: http://dev.mysql.com/doc/refman/5.1/en/alter-table.html

Perhaps you are referring to primary keys vs secondary indexes, for which there is a difference in how they are physically stored on disk and in memory, particularly with InnoDB. There is a substantial performance gain to be had by having a relevant primary key that is referenced in the where clause as the data is stored in the same page as the primary key, both on disk and in the buffer pool. Secondary indexes reference the primary key, thus require two lookups.

AaronBBrown··on Ex-Facebookers launch MemSQL (YC W11) to make your database fly
Riak is a great product with an incredible support team, if you choose to use their support.
AaronBBrown··on Ex-Facebookers launch MemSQL (YC W11) to make your database fly
MEMORY tables have table-level locks and from a concurrency perspective, is just as bad as MyISAM, so really offer no advantage unless there is only a small number of consumers. A well tuned InnoDB table will outperform the MEMORY engine )(after the warm-up period) as soon as you have more than a handful of users performing write operations.
AaronBBrown··on Ex-Facebookers launch MemSQL (YC W11) to make your database fly
Can you explain this further? How is using a temporary table faster? Explicit temporary tables are simply regular tables that only last your current session. Do you mean the MEMORY storage engine? What do you mean by "don't use keys, use indexes?" The term KEY and INDEX in MySQL are exact synonyms.
AaronBBrown··on Actually using Ed
Agreed, but the point was that there are very very few legitimate reason in 2012 to use ed unless you just happen to like it.
AaronBBrown··on Actually using Ed
Can you give a specific example? I have a not insignificant amount of experience with thousands of servers under my belt and I have yet to ever need to type "ed" into a server. I did find edlin useful in DOS 4, but that was ancient times.
AaronBBrown··on Actually using Ed
Having been a user of *NIX for over 20 years and a professional Systems Administrator for over 10, I have never once had a reason to use ed. Even the smallest embedded environments usually have some variant of vi available. The only time that I've needed to use ed was edlin in the dark days of early MS-DOS, which is very similar. This is borderline masochistic.
AaronBBrown··on Ampex - concise readable Ruby blocks
I'm curious about the performance overhead of this vs using traditional syntax with named variables. Looking over the gem, the code is quite terse, but it depends on method_missing, which is notoriously slow. The danger with an abstraction like this is that it can make performance problems difficult to identify since it looks so much like a built-in operator.

I also agree with stuffihavemade in that I don't actually find

   (&X.method(bar))
any more clear than

   { |x| x.method(bar) }
AaronBBrown··on Goodbye, MongoDB
As a paying customer of Basho who has had several direct experiences with sales and technical support, I second this. They are incredibly helpful in the event of a problem and are passionate about educating their customers to provide the highest chance of success with their products. They are honest about the limitations imposed by Riak and will go out of their way to help identify a solution. I have literally never had as positive an experience with a technical support team as with Basho. It is very refreshing.
AaronBBrown··on Migrating From MongoDB To Riak At Bump
Thanks, papsosouid. Facts are much more useful to discussions like this. It still doesn't change the fact that PHP is capable of running the most trafficked sites in the world (side note: I don't like PHP, either. I just hate haters who can't see the world in shades of gray). Having heard Facebook engineers speak about MySQL many times, I have not seen any inclination that they are dissatisfied with MySQL as a platform choice. (And please, no one reference on that utterly BS article published on gigaom.com)
AaronBBrown··on Migrating From MongoDB To Riak At Bump
So, you have no facts, just bias. Thanks.
AaronBBrown··on Migrating From MongoDB To Riak At Bump
What do you base that on?
AaronBBrown··on Migrating From MongoDB To Riak At Bump
I said capable, not awesome, or cutting edge, or the only thing you'll ever need, or the best thing since sliced bread. Capable is very different from your obviously flawed analogy. Windows 3.1 and the original Macintosh were successful at the time because they were capable products at the time which have evolved into the good, but not flawless products that exist today.

The groupthink MySQL/PHP hate here implies these are terrible products which only a moron with bad taste would use, which is demonstrably false when you look at the choices made by those using them.

AaronBBrown··on Migrating From MongoDB To Riak At Bump
Bitcask is specifically designed around not doing random I/O, particularly for writes. A bitcask back end is essentially a gigantic sequential transaction log.
AaronBBrown··on Migrating From MongoDB To Riak At Bump
It proves that the technologies are capable products at the most massive scales. Do you have evidence to support that Facebook, Tumblr, or Etsy would have been better off had they chosen different technologies (of course not)? Or that they made things more difficult for themselves? How would Facebook be improved by PostgreSQL? At scale, data is so massively partitioned that the fact that you don't have windowing functions is utterly irrelevant. I hate PHP as much as the next guy, but the facts are that it gets the job done. And that, in business, is what matters. The angst on here about MySQL is unfounded and is largely a symptom of groupthink.
AaronBBrown··on Migrating From MongoDB To Riak At Bump
MySQL Cluster, Percona XtraDB Cluster, Clustrix, Continuent Tungsten Replicator, vitess, and a number of other products are available in the MySQL ecosystem designed around these types of problems.
AaronBBrown··on Migrating From MongoDB To Riak At Bump
By that, you mean used effectively on some of the largest, most profitable websites in the entire world? ;)
AaronBBrown··on Life Below 600 Pixels
Have they actually done usability studies on this or are they just making stuff up?
← PreviousPage 5 of 5