Possible Efficiency Improvements Related to BeautifulSoup? #74
Right now, running BeautifulSoup on the output HTML page (and running through the tree to find our custom tags) takes up the bulk of page load times. This is especially true for large/complex HTML output. I wonder if it would be better to run these processes a bunch of times, on small pieces of the page as they're being assembled (e.g., as they're being put into
cs_problem_spec) rather than doing one big pass at the end.
Maybe worth experimenting.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?