Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

acme (189)

acme
  (email not shown publicly)
http://www.astray.com/

Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.

Journal of acme (189)

Monday January 08, 2007
09:15 AM

Falcon

[ #32098 ]
MySQL released its new storage engine: Falcon. It makes some good assumptions which weren't true a few years ago: lots of memory, fast CPU, still slowish disk. It still needs a little optimisation though, as the first microbenchmarks show. I like how MySQL has become a database system with many storage engines: pick the one which suits your needs.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 'It makes some good assumptions which weren't true a few years ago: lots of memory, fast CPU, still slowish disk.'

    I'm not sure about the "lots of memory" assumption anymore, personally -- look at all the VMs and Xen instances people are using nowadays, they generally don't have such generous RAM allowances as a dedicated machine would.

    • Sure, but why would you deploy a performance critical database in an environment (virtual or not) with little memory in the first place?

      In my experience you either need the performance for production, or you need the flexibility of virtualisation for development and testing.

      In the latter case performance is rarely important. I mean, it would be nice to have it, but it's not why you do it.