Skip to main content

Diigo Home

Re: Mass Mailout Performance Tips - The Diigo Meta page

www.mail-archive.com/...msg29120.html - Cached - Annotated View

Joel Liu's personal annotations on this page

joel
Joel bookmarked on 2008-03-06 mass performance qmail
  • There is a qmail patch (big concurrency) that will allow running more
    remotes. The default kernal in RedHat 6.1 limits you to 512 total processes
    and half that per user. I have recompiled the kernel for 2560 total
    processes and 2048 per user. See the file
    /usr/src/linux/include/linux/tacks.h.
  • I can get about 50K emails per hour using 400 remotes. That would take 10
    hours with your list. The qmail queue size seems to stabilaze between 10K
    and 15K during the run. There is usually between 300-400 remotes running.
  • I am currently experimenting with bypassing qmail altogether. Using shared
    memory I fork off 1000 child processes to chew on a list in parallel. Each
    child will call qmail-inject only if its direct attempt fails. My testing
    is still rough but it looks like I can get a 5 to 10 fold improvement.

This link has been bookmarked by 3 people . It was first bookmarked on 06 Mar 2008, by Joel Liu.

  • 06 Mar 08
    joel
    Joel Liu

    mass performance qmail

    • There is a qmail patch (big concurrency) that will allow running more
      remotes. The default kernal in RedHat 6.1 limits you to 512 total processes
      and half that per user. I have recompiled the kernel for 2560 total
      processes and 2048 per user. See the file
      /usr/src/linux/include/linux/tacks.h.
    • I can get about 50K emails per hour using 400 remotes. That would take 10
      hours with your list. The qmail queue size seems to stabilaze between 10K
      and 15K during the run. There is usually between 300-400 remotes running.
    • 1 more annotations...

Top Tags