filtering performance question about groq-js HOT 2 OPEN

I'm running into similar performance issues. I'm attempting to make a reusable groq testing library, and for some queries across 1500 entries, it's taking 15+ seconds. These queries are perfectly fast in production.
I assume that the lack of indexing would essentially prevent this from running any faster ... do you think there's any possibility that groq-js could add support for indexing?

from groq-js.

So far my queries aren't particularly complex, but regardless of their complexity, runtime for groq seems linear and dominated by the number of records in my input.

This is expected. groq-js is a naive implementation and doesn't index the documents in any way to speed up query performance. Right now there's no performance gain of using groq-js vs. just calling .filter(…) in JavaScript.

which takes 5662ms.

As for the performance itself: There hasn't really been done any specific work in making it efficient. There might be a lot of low-hanging fruits which can speed up performance.

from groq-js.