2011/5/25 kushal soy <[email protected]>: > Stefano, > > I didn't get solution suggested for disk access bottleneck , can you > please explain me again.
If you use many processors in your spoolmanager configuration you can try reducing them so that the big emails needs few/no processor changes. If you already use few processors then try to use faster disks. Stefano > Thanks > > On Wed, May 25, 2011 at 12:44 PM, Stefano Bagnara <[email protected]> wrote: > >> 2011/5/25 kushal soy <[email protected]>: >> > Hi, >> > >> > my mail client is sending java mail with attachment(size:250 KB). >> > but even with increasing session(independent thread), the client deposit >> > speed is slow( ~5msg/second). with lower size, client deposit become much >> > faster though. >> > also tried with smtp-source for large body size. >> > [time ./smtp-source -s 50 -l 256000 -m 5000 -d -c -f [email protected] -t >> > [email protected] localhost:25] >> > >> > >> > currently, performance data in James page is of 100 bytes of body >> data.[*time >> > smtp-source -A -C1500 -l 100 ..*.], which doesn't hold for large size. >> > >> > >> > what is the expected performance of James with mail attachment? >> >> The problem is probably disk access. James writes and reads the full >> message to file/db many times and this is a bottleneck. >> You can reduce your processors making sure the most used "way" is >> defined in the root processor. Whenever a message is moved from one >> processor to another it gets written again on disk. >> >> Stefano >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
