submit.cfg best practices

NathansDIS

Hello All-

I have a question about best practices for setting file permissions with submit.cfg. Here is the scenario: I can specify the permissions for a particular branch with 50 rules in an easily-readable format. However, I can also specify the same permissions for this branch with 20 rules albeit in a hard-to-read format.

My question is this: Given 10 branches of this size, is it going to be a major performance hit to have 300 extra rules in submit.cfg? I usually err on the side of readability and ease of administration, but don't want to create a performance problem either. Has anyone dealt with this decision before that could share their experiences, suggestions, flames, etc?

Thanks in advance for your time,

-Nathan
Washington State DIS
~~~

Adam Stoller

I'm not aware of any significant performance issues related to the number of rules specified in the submit.cfg file - though that doesn't mean there isn't any.
You should probably check with Support too, if you haven't already.

About the only other suggestion I can make is to try it out yourself.
Create two versions of the submit.cfg file - then time the submission of a file that matches a rule near the top of the configuration and one that matches a rule at the bottom of the configuration (and potentially one that doesn't match any rule?) - do this with each of the configuration files (remember to run iwreset when you change config files).

It would be interesting to see what you find out.

A fairly simple way to time this would be to use a simple script - either from the command line, custom menu, or even a workflow that registers the time, performs the action, and registers the time again - something like this might work:#!/path/to/iwperl
use strict;
use warnings;
use TeamSite::Config;
require 'sys/syscall.ph';
#----------------------------------------------------------------------
# Preamble - make sure file is modified in preparation for submitting
#----------------------------------------------------------------------
die "Usage: $0 vpath-to-file\n" if (!@ARGV);
my $iwhome = TeamSite::Config::iwgethome();
my $iwmount = TeamSite::Config::iwgetmount();
my $fvpath = shift;
my $now = time();
utime($now, $now, "$iwmount$fvpath");
#----------------------------------------------------------------------
# Initialization of time information
#----------------------------------------------------------------------
my $TIMEVAL_T = "LL";
my($done, $start);
$done = $start = pack($TIMEVAL_T, ());

syscall(&SYS_gettimeofday, $start, 0) != -1 or die "gettimeofday: $!";
#----------------------------------------------------------------------
# Perform the submission
#----------------------------------------------------------------------
system("$iwhome/bin/iwsubmit $fvpath TIME_TEST");
#----------------------------------------------------------------------
# Get end time information and determine time delta
#----------------------------------------------------------------------
syscall(&SYS_gettimeofday, $done, 0) != -1 or die "gettimeofday: $!";

my @start = unpack($TIMEVAL_T, $start);
my @done = unpack($TIMEVAL_T, $done);
# fix microseconds
for ($done[1], $start[1]) { $_ /= 1_000_000 }
my $delta_time = sprintf("%.4f", ($done[0] + $done[1]) - ($start[0] + $start[1]));
print "DELTA: $delta_time\n";I'd be interested in hearing the results of your tests...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com