Re: hardware specs
Tahir Chaudry <[email protected]>
| Newsgroups | gmane.mail.majordomo.general |
|---|---|
| Message-ID | <BFDAAD14.46AEA%[email protected]> |
again, thank you so much for such a great and detailed answer. you¹ve helped a lot, and because of you, I have all my answers. thank you again. : ) tahir On 12/30/05 12:25 AM, "Daniel Liston" <[email protected]> wrote: > Your mileage may vary, but in terms of space, power, performance, > price, and heat, you may find the T1000 to be a better deal for > about the same price as the v210. In my opinion, they are both > noisy, but most people do not keep either one under their desk. > > I have dequeued 375,000 messages from a Sun MTA on a sf440 class > server across a gigabit network to a Sun mailstore with the new > Niagra (CMT) processor and beta storage arrays in 30 minutes. I > doubt you will ever see this kind of performance when you have > forces outside your control acting against you, like destination > MX hosts off-line, DNS corruption, maximum recipient restrictions > with all the major online providers, etc. > > To really answer your question, is the v210 big enough? That is > dependent on how many messages you need to send to your million > users each day, or how many lists with a million subscribers you > have. I like to err on the cautious side, but you need to do the > math. How many messages of what size to how many distribution > lists with how many zubscribers per day/week/month whatever? > > You might be able to get more than 40 msg/sec off the system, but > even if you got 10 recipients per/msg successfully delivered, > 100,000 / 40 is still 2,500 seconds, or about 42 minutes that has > to be dedicated to each distribution. Even getting 10 rcpt/msg > is a bit optimistic. Worst case scenario, going with a single > rcpt/msg, you are looking at 42 minutes stretching to 7 hours. > > All these figures do not take into account the CPU or disk I/O > that would be required to queue the mail until delivered. The > way majordomo works, is one message to all one million recipients. > Very little disk space, but also makes delivery a serial process. > To optimize delivery, you create more messages with less addresses > per message to be delivered. This eats more CPU and more disk > just to prepare for delivery. > > Sorry I could not give you an exact answer, > Dan Liston > > Tahir Chaudry wrote: >> > Dear Dan, thank you very much for your response. We are only sending >> > out the mail, it is more of announcements only email. >> > >> > Thank you for a great insight about the bandwidth. Do you believe >> > we need a bigger server if the bandwidth is under control? >> > >> > Thank you again, >> > >> > Tahir >> > >> > >> > -----Daniel Liston said----- >> > >> > The server you are thinking of might be a bit weak for the size >> > of the mailing list(s) you are considering. On the other hand, >> > if you are running an announcement only (no replies or other >> > interaction by your zubscribers), you might be looking at up to >> > 40 msgs/sec output with a really fast MTA and 7Mbps connection. >> > One outgoing distribution, on a 35k message requires 1.4Mbps of >> > bandwidth to support 40 msg/sec. >> > >> > One of these lists distributing a 35k message would eat a full >> > T1 pipe for over 7 hours. If you have varied bandwidth between >> > sending and receiving data, it is your send pipe that can fill >> > up. This calculation assumes a separate message for each and >> > every recipient totalling 35Gb of data to move across the pipe. >> > >> > How long does it take you to copy 35Gb of data from one computer >> > to another on your local (100Mbps?) network? Now factor in the >> > speed of your internet connection. >> > >> > Dan Liston >> > >> > Tahir Chaudry wrote: >>> > > I need to setup a majordomo server for around 1 Million emails per user >>> > > list. >>> > > >>> > > we must use sun server. any idea what type of server would do the job? >>> > > >>> > > I was thinking V210 2x1.2GHz CPU plus 4 GB RAM. >>> > > >>> > > -- tahir >>> > > >> > >> > > -- tahir