any ideas to improve performance of trivial resolvers (think alias-resolver) better when using core.asyns’s threadpool for execution? My usecase is that on my entity I have a lot of entries with keys where I wrote an alias resolver for each one. Pathom is essentially doing the job of clojure.set/rename-keys at this point, but the context switches kill the performance (since there are a lot of tiny resolvers to execute)

I could write a single resolver which does the job with clojure.set/rename-keys but since there is no support for optional inputs (there is an issue for that) it cannot be currently expressed

@thenonameguy one question first, why do you need so many renames? if you are loading from some source that doens't have them, is it possible to convert when you fetch it on the first time?

it’s part of our domain

we had a short uuid based name for some of our fields

and there is a corresponding human name

ok, that's a valid case, just not optimized if you using a lot of them

another thing to consider is, do you need the parallel parser? although I keep recommending it as the default, I'm starting to believe that for most people the serial parser may be a better option

the question is, does the queries you run have parallelism opportunities? usually if its a single or a few datasources that may not be the case, and them you are just paying the higher overhead and complexity price of using the parallel parser