[seqfan] Re: Submission suggestion

Richard Mathar mathar at strw.leidenuniv.nl
Sun Nov 6 23:32:52 CET 2011

We read in http://list.seqfan.eu/pipermail/seqfan/2011-November/015795.html

dww> As display, the %STU lines determine which elements are shown in various 
dww> sequence
dww> views (the sequence page, the internal format page, the list page, the 
dww> pin plot, etc).
dww> This adds conflicting display requirements. For example, we don't want 
dww> to display too
dww> many elements, so we must keep the %STU lines down to 260 characters, we 
dww> don't
dww> want enormous values in the %STU lines, etc. This creates issues for the 
dww> submitter
dww> when entering sequences; they cannot include too many terms, etc.

It's evident that for performance reasons the main database needs to 
contain a small snapshot ( say 3 lines with roughly 80 bytes each)
of anything bigger than that. As Russ already pointed out, you do not
want to scan tons of b-files each time anyone clicks on a button
or searches for a number. The splitting between the actual few hundred
bytes in the main database and the implicit link to the b-files is 
exhibiting exactly this real-world limitation of computational resources.


More information about the SeqFan mailing list