#### Description
> (Please provide the context of the performance review, and describe how the feature or service works at a high level technically and from a user point of view, or link to documentation describing that.)
The #anti-harassment Tools Team will be building a new extension for the #ip_info feature. The [[ https://meta.wikimedia.org/wiki/IP_Editing:_Privacy_Enhancement_and_Abuse_Mitigation/IP_Info_feature | project page ]] gives a detailed description of the project.
Effectively our extension will provide information //about// an IP address without (1) the need for the user to use an external service themselves and (2) exposing the IP address itself to the user. This provides the user with any details they could have retrieved from knowing the IP address. This information could be displayed in various ways (hover card, special page, etc.).
We plan on building an API endpoint (REST and/or Action) that takes an edit id or log id and returns data about the IP addressed used for that action. For anonymous actions it would provide a result to all users (who are logged in?). This endpoint //may// provide a result to checkusers for actions performed by logged in users. Regardless, the data will only be returned for actions performed within the previous year (?) for anonymous actions and 90 days for actions performed by logged-in users.
Based on our investigation in T259726, the data our users are looking for is not accessible from freely licensed datasets. Therefore, we will be looking to purchase a license to a proprietary dataset (or using one we've already purchased).
#### Questions for #performance-team
TBD by @dbarratt
#### Preview environment
> //(Insert one or more links to where the feature can be tested, e.g. on Beta Cluster.)//
>
> Hosting the changes on Beta Cluster is a requirement prior to performance review. Please ensure that the feature can be used directly on the link(s) provided, without any data entry such as having to create an article. Any sample content needed should already be present.
>
> If the changes cannot be hosted on Beta Cluster, explain why and provide links to an alternate public environment instead where the Performance Team can also SSH into. Links to code only is insufficient for a performance review.
TBD
#### Which code to review
> //(Provide links to all proposed changes and/or repositories. It should also describe changes which have not yet been merged or deployed but are planned prior to deployment. E.g. production Puppet, wmf config, or in-flight features expected to complete prior to launch date, etc.).//
TBD
#### Performance assessment
> Please initiate the performance assessment by answering the below:
>
> - What work has been done to ensure the best possible performance of the feature?
> - What are likely to be the weak areas (e.g. bottlenecks) of the code in terms of performance?
> - Are there potential optimisations that haven't been performed yet?
> - Please list which performance measurements are in place for the feature and/or what you've measured ad-hoc so far. If you are unsure what to measure, ask the Performance Team for advice: [[ mailto:performance-team@wikimedia.org | performance-team@wikimedia.org ]].
TBD