[SERVER-74838] Evaluate benefits of adopting Arm's optimized routines Created: 14/Mar/23 Updated: 21/Mar/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | perf-servicearch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
This is intended to be an umbrella ticket for adopting Arm's optimized routines from the following repo: https://github.com/ARM-software/optimized-routines We should evaluate the performance implications of using these optimized routines when targeting aarch64. For example, we may benefit from using optimized string routines: https://github.com/ARM-software/optimized-routines/tree/master/string/aarch64 |