Maximum job size is reported by the stats command,
documented here:
https://github.com/kr/beanstalkd/blob/v1.4.6/doc/protocol.txt#L566
Admittedly, this document isn't the most obvious place
for beanstalkd users to look.
You can control this value with option -z on the command line.
The default is somewhat arbitrary: 65,535 bytes.
kr
$ beanstalkd -h
Use: beanstalkd [OPTIONS]
Options:
[snip...]
-z BYTES set the maximum job size in bytes (default is 65535)
Thanks. don't know why I didn't think to check the help in the program.
Are there many downsides to allowing larger jobs? 256k or so? Similarly, is there a performance increase by restricting the job length to something smaller like 1k or 512 bytes?
Thanks, Aaron
This option doesn't affect speed at all.
Performance depends only on the actual jobs you put in the queue.
The server doesn't copy a job once it has been read from the network,
but larger jobs still take longer to receive and send.
kr