Hi Bigger than my experience, so just a suggestion - have you looked at replication?
If you have a master which does all the processing and (multiple) slaves which handle all the reads then you might benefit from cheaper Intel hardware and have a more robust system to boot. Good luck! Peter ----------------------------------------------- Excellence in internet and open source software ----------------------------------------------- Sunmaia www.sunmaia.net tel. 0121-242-1473 ----------------------------------------------- -----Original Message----- From: spiros [mailto:moka@;hol.gr] Sent: 21 October 2002 00:00 To: [EMAIL PROTECTED] Subject: Tips for LARGE system I need to come up with an intra-company system recommendation: We are looking at a possibly huge system getting data from a LAN(No web-based app or anything-in fact it will NOT be connected to the web) handling from 3M to 20M records/day with potentially a lot of processing, live inserts/ updates etc. I have a demo version(running on a PIII 2x1000MHz, 2GB RAM Linux machine) but it cannot handle the full load. I am thinking of keeping Mysql 4-0.4. and going to an alpha machine(running linux). The question is whether anyone has done this before. So I am looking for tips and recommendations(before buying any hardware): 1) Are there any known or expected problems with Mysql on alpha machines? 2) Do I need a special linux version(the kernel I use says 2.4.18-4GB, but I need much more RAM and in fact this is the main reason for going to an alpha machine)?(never used linux on anything except Pentiums) 3) Are there any guidelines in estimating more presicely what hardware I will need? 4) I cannot foresee all the possible growth, nor will the initial budget be huge. Is it then woth planning for building out / clustering for some redunacy and some load balancing upfront 5) Suppose I get this system running. What are the problems in keeping it running? Critics say that a)"data management is a pain" b) "scalability is pretty non-existant (just sticking more RAM)". I though it would be much cheaper to stick in more RAM than going to another RDBMS c) "it lacks a load of fundamental features of large RDBMS". I thought 4.1 should be out between end of Octobera nd January, and it will have triggers, no? 6) How is a hot backup organized in Mysql(i.e. backing up the data while the database is running) 7) I'd also appreciate any input from people who have used official mysql support before. Hopefully there will be a set of issues: a) hardware requirements b) setting up and configuring(i.e. specifying InnoDB buffer sizes) c) performance tuneup. Again, I'd appreciate any info from mysql people or people who used mysql support before. My problem is that from mysql support I am told we can discuss all these after signing a support contract, but to get there I need to come up with a company realistic cost estimate that includes the necessary hardware... I'd appreciate any input from people running such systems. I have never used any other RDBMS, so I am cannot judge if the critisism is justified or not and would appreciate any help on this Thanks, S.Alexiou --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
