This MySQL server has been running for 6 days, 19 hours, 39 minutes and 5 seconds. It started up on May 21, 2004 at 04:24 PM.
* *Server traffic*: These tables show the network traffic statistics
of this MySQL server since its startup.
Traffic ø per hour Received 638,362 KB 3,901 KB Sent 110,770 KB 693,111 Bytes Total 749,133 KB 4,578 KB
Connections ø per hour % Failed attempts 2,604 15.91 0.09 % Aborted 7,406 45.25 0.26 % Total 2,815,609 17,204.92 100.00 %
* *Query statistics*: Since its startup, 228,607,570 queries have been sent to the server.
Total ø per hour ø per minute ø per second 228,607,570 1,396,917.99 23,281.97 388.03
where 84% of that are selects and 12% are updates and 1.14% are new inserts whole db has about 3.6 GB of data
Brent Baisley wrote:
You wouldn't setup one repository to hold the data. You would actually probably hit disk and network limitations with a single repository. MySQL supports master/slave setups which would replicate the data across machines. One machine would be the "master" handling updates which would propagate to the slaves.
On May 27, 2004, at 9:30 PM, tachu wrote:
WOuld the following scenario be possible
I currently have about 1.2 Tb of data that i need to transform into mysql and be able to server a very high amount of pages from a discussion board. would i be able to place the mysql/data directory in a main server with huge storage and then have several mysql server instances running on different machines accessing the same /mysql/data directory? would there be any limitations. i need to be able to server about 200/sec on each server and have about 40 servers. basically my ideas is to have several mysql servers running but one main data repository. any help is appreciated
Thanks
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
