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
Matts (1087)
Matts
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
Tuesday January 28, 2003
11:08 AM
More on SQLite vs MySQL vs PostgreSQL
D. Hipp sent me his benchmarking code, so I ran it on my optimised Pg box. The optimizations are really just giving Pg some real memory to chew on. This box has 4G of ram, and Pg out of the box is optimized for a box with 8M of ram (no, really!). My config is here if you're interested.
One thing to note is that the tests use the sqlite (and psql) command line tool, whereas a better test for perl hackers would be one using DBI. But this thing is written in tcl, and I don't want to hack on it any longer than absolutely necessary!
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Hmm... (Score:1)
Re:Hmm... (Score:2)
nosync?? (Score:1)
Re:nosync?? (Score:2)
results 404 (Score:1)
Re:results 404 (Score:2)