Heard scary things about Oracle from an admin point-of-view, but expect
unfortuantely I'll need to look at that in the future. Figured it
would be
relatively trivial to do (write driver).. Keep hoping MySQL will have
two-way replication soon with write locks and then it's all solved :o)
Just done a bit more about database partitioning (oracle, db2) and
looks
quite good. Does anyone know of an easy-to-manage (like MySQL) and
cheap
database that does two-way replication and partioning?
SAPdb can do that, but it is not really easy to manage. Actually, the
one
database that is quite easy to manage and has a lot of scaling potential
is SQL server from M$ (they bought it, so that's why it's quite good,
in case
you're wondering ;). But you'd need a wind.. server for that and that
sux. I heard db2 was quite easy to manage. Ilja is working on a setup
for
one of our clients right now, he'll be able to tell if it is easy.
- you'll need the LMTP daemon, not dbmail-smtp (increase in speed and
handling is about 1000%).
I've just checked 1.x cvs and 2.0 cvs and can't find anything (except
in the
TODO list) about LMTP. Can you advise when this is planned for?
Well, Aaron has been working on an LMTP daemon, it is in his big patch.
Since i forgot about that i've been working on one also and that one is
sitting
here on my laptop :) I've done some testing and in stead of 4 - 8
messages (dbmail-smtp)
per second it can do over 300 messages per second with a better
database load
(since the db doesn't have do handle new connections all the time).
SMTP load will
also drop since the lmtp daemon talks directly back to the SMTP and
doesn't need
to sent seperate bounces and stuff like that.
An LMTPd will be in the 2.0 release.
- Dbmail 2.0 will have a lot of imap optimalization which
will increase performance a lot.
My main stress for scalability is the database load -- I don't care
how many
front-end servers I have, so if the front-end servers have to grind
away
that's fine.
ok :)
To answer on Matthew's message:
The development branch doesn't have all these optimizations yet, but
they
are planned before the 2.0 release. The new database model in 2.0 will
help with that.
- use a native webmail like webDBmail.
Yep, we've written one already which works nicely -- I think that's
what's
helping us scale at the moment - as we don't have heaps of imap webmail
clients hammering away at the database. I'd love to use one-way
replication
with MySQL and point the webmail at that, but I got told about the
issues
with writes being delayed, etc so gave up on that -- but otherwise it
would
be perfect.
MySQL is a fairly good database for fast data storage and retrieval
work.
Advanced features are not even close. I think that the merger between
MySQL
and SAPdb is the solution. MySQL will be the lightweight and the new
database
will be the heavyweight.
We currently have a db2 licence laying around. We might write
a driver for that and test for speed.
Anyone know what the cost is for DB2 (real cost) for a 2-4 server
system?
Ideally 2 partitioned main servers which are replicated for backup to
second
two servers?
I have no idea :)
You could also hire us to tune a monsterous dbmail system for you.
We're already doing some very big dbmail setups. ;)
I once started dbmail with the thought of a multi-million
based e-mail system with super ease of use and maintenance.
That would actually be great, as I've been thinking that my current
setup is
not tuned very well. Been looking around for a local (New Zealand)
MySQL
expert, that would come in a cheaper than the MySQL.com's $3,500+
offering
:( Get in touch and let me know your rates, estimated cost, etc.
I'm going to ask Roel to contact you (i'm at home these days :).
Best regards,
Eelco
/Mark
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_________________________
E.J.A. van Beek
ICT Manager
IC&S
T: +31 30 6355730
F: +31 30 6355731
PGP-key:
www.ic-s.nl/keys/eelco.txt
