[Spread-users] Configuring Spread for bursty traffic

[Sam Chen]

According to this post,
http://commedia.cnds.jhu.edu/pipermail/spread-users/2001-May/000084.html
it seems that they can be set up high as "tens of thousand".

I also have the same problem on the receiver' end. In my application, the
messages are sent to a receiver and logged using the following PERL code:


use Spread;

.....
Spread::join($mbox, SPREAD_GROUP); # join the group
.....
for(;;) {
    $current = time();
    if ($current > ($stamp+GAP*60)) { # GAP == 5 minutes, used to rotate the
logs
        $fh->close;
        ($stamp, $dir) = get_stamp_dir(GAP, ARCHIVE, $current); # ARCHIVE is
a top directory
        $fh->open($dir."/".$stamp, O_WRONLY|O_CREAT|O_APPEND) or die("Can't
open $stamp in $dir\n");
    }
    my @readable = $select->can_read;
    for (@readable) {
        my ($service_type,$sender,$groups,$mess_type,$endian,$message) =
Spread::receive($mbox);
        if ($service_type & REGULAR_MESS) {
            print $fh $message;
        }
    }
}

The program works for about a few hours, then suddenly nothing is shown up
in the log files while the CPU is going up to 100%, apparently due to the
fact that the application is dropped off by SPREAD and it goes into the "for
(;;)" circle.

Can my problem be solved by raising WATER_MARK and MAX_SESSION_MESSAGES to
very high values, maybe 10,000 - 100,000 ?


Sam



On 9/18/07, Vivien Quema <Vivien.Quema at inrialpes.fr> wrote:
> Hello,
>
> I am testing spread with a bursty application (processes send bursts
> of 10000 messages, each message having a size of 1kB). I have seen
> that it was possible to change the WATER_MARK and
> MAX_SESSION_MESSAGES (they have for default value 500 and 1000
> respectively).
>
> Which value do you advise me?
>
> Thanks for your help,
> Vivien
>
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.spread.org/pipermail/spread-users/attachments/20070927/75e64ec3/attachment.html