Details
Details
- Reviewers
tomek atul inka rohan - Commits
- rCOMMc3231ddf2158: [lib] Use RadixTree in SearchIndex
- I tested the chat mentions experience
- I did some perf testing:
In combination with the previous diff, I used this patch to test performance before and after this change. I made sure I had at least three samples of each scenario. Will also link my messy Gist of results, but it's not really interpretable by anyone other than me.
Here's the relevant portion:
BEFORE LOG useChatMentionSearchIndex took 1801ms LOG useChatMentionSearchIndex took 1748ms LOG useChatMentionSearchIndex took 1730ms LOG useChatMentionSearchIndex took 1831ms AVERAGE 1777.5ms JUST DEDUP (parent diff) LOG useChatMentionSearchIndex took 1027ms LOG useChatMentionSearchIndex took 949ms LOG useChatMentionSearchIndex took 957ms AVERAGE 977.7ms DEDUP + RADIX TREE LOG useChatMentionSearchIndex took 643ms LOG useChatMentionSearchIndex took 629ms LOG useChatMentionSearchIndex took 651ms LOG useChatMentionSearchIndex took 609ms AVERAGE 633ms JUST RADIX TREE LOG useChatMentionSearchIndex took 1394ms LOG useChatMentionSearchIndex took 1468ms LOG useChatMentionSearchIndex took 1511ms LOG useChatMentionSearchIndex took 1492ms LOG useChatMentionSearchIndex took 1397ms AVERAGE 1452.4ms
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
lib/shared/search-index.js | ||
---|---|---|
66 | Can this be simplified? |
lib/shared/search-index.js | ||
---|---|---|
66 | I tested this approach in the Chrome debug console and found that it didn't work: |
lib/shared/search-index.js | ||
---|---|---|
66 | Ah, that makes sense. In order to make it work, we would need to bind the method which will be more complicated than the current solution. |