To stress-test FlexSearch,

• I created 5000 markdown documents where the content for each was randomly sized between 750 words and 2000 words.
• Eleventy translated these 5000 documents into a 8mb Json file.
• FlexSearch took about 2/3 of a second to index that Json document on each page load.
• Chrome showed the tab using 200-300mb of memory (which was pretty much what my browser showed Amazon using)