One of the tasks I'm hoping to achieve with help from other open-source developers is to identify, and create JIRA issues for, the most commonly used elements within the Second Life source-code. The kinds of things I'm hoping to identify are things like:

1. 1. Commonly accessed library functions ##
      What do these library calls do, and how well do they do it? Do we really need to call this function here, can it be delayed or performed in the background somehow? Are there better alternatives? Would a local function be more efficient?

1. 1. Commonly executed functions ##
      Are there any functions in the code that are executed significantly more than others? What can we do to reduce the frequency these are called, or perform the task they do more quickly? Is the function poorly optimised for a particular platform?

1. 1. Big loops ##
      Are there any loops or intensive operations that the viewer spends a lot of its time in? Do these cause blocking? Can we somehow reduce the time these require, or perform the task in multiple smaller chunks? Is there a way that we can perform only a part of the work and continue, while doing the rest as a background task for later?

1. 1. Hacks or high dependency ##
      Is the solution hacky, or otherwise done in a way that may potentially fail or cause issues? Is an element highly dependent on other elements that are not strictly related or which could result in bugs should one of these dependencies change? Can these dependencies be taken out?

It would be good if all open-source developers who've seen things that meet these criteria could create JIRA issues and attach them here. It then becomes easy for other open-source developers (or even interested Lindens) to investigate these functions, libraries etc. and evaluate whether they require further work and pick them up as required.
I'd like to encourage developers who identify functions like these to hand them off here where possible. This allows developers working on issues to concentrate on their own task, while ensuring that someone will come back to it later.

1. 1. META ISSUE ORGANISATION ##
      If you believe you've found a function or area that fits the purpose of this meta-issue, then please create a JIRA issue for it, then add a link to one of the sub-tasks for this meta-issue (or create one if none are appropriate). Do NOT link JIRA issues to this meta-issue directly, it is likely to feature far too many issues for this to be feasible.

Developers investigating issues linked to here should first look to see if someone is assigned. If not then you may investigate the code from an evaluation perspective, determining if it is in fact an appropriate element and is not already sufficiently optimal. If the element is not appropriate then it should be un-linked. If it is believed to be optimal already then please comment with a description but DO NOT CLOSE unless several developers have come to the same conclusion. Already optimal code needs no further work unless it can be proven to be inefficient.

If an element is not optimal, and you are able to work on it, then please assign the issue to yourself and submit the patches as progress is made. Please provide at least rudimentary benchmarking of the affected element ONLY to illustrate any improvement being made.

1. 1. Conclusion ##
      The tasks here may not be the most interesting, but in my opinion they may be some of the most rewarding in terms of performance or future development benefits. These should hopefully be ideal tasks for in between other open-source projects or development.